The plugin should be called before vite/plugin-react
or vite/plugin-react-swc
for accurate sourcemaps
#336
+17
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context: React + Vite
I noticed that when the plugin is called after one of
@vitejs/plugin-react
or@vitejs/plugin-react-swc
, it may result in inaccurate sourcemaps. I have manually tested this in 2 of my local apps. Listingcode-inspector-plugin
before or after these two plugins was resulting in two different DOM sourcemaps. The filePath information was always correct, but the line number information was changing immensely, in the scale of tens of lines, depending on the size of the file.So I have kindly made a small addition that only affects the Vite plugin.
I'm using the following versions:
I didn't test this thoroughly, however if this caveat is correct, it can be added to the documentation site as well. (Sorry if I missed an already existing one)
Correct way to use it:
Thank you!