fix: Sourcemap issues in production build #312
Merged
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.
It was reported that vite based projects had a familiar
sourcemap
warning when serving.Because of the way we were passing the
--sourceMap false
to the production workflow build, sourcemaps were slipping in. This changeset ensures that thetsc
step in each package correctly has the flag applied.Tested in both a standalone react and react-native project with a dev release. The vite-based react project no longer shows the reported sourcemap warnings.