chore: fix source map support when developing Vite #20167
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sapphi-red
force-pushed
the
chore/fix-source-map-support-when-developing-vite
branch
from
b14e21b to
4ddd23e
Compare
Member
Author
|
Merging as this is probably not controversial |
sapphi-red
deleted the
chore/fix-source-map-support-when-developing-vite
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
source map support when developing Vite was not working because the sourcemap was not output. This PR fixes that.
This PR also replaces
source-map-supportwithprocess.setSourceMapsEnabled(true)becausesource-map-supportdoes not supportcauseproperty (evanw/node-source-map-support#337).refs #19925