hide sourcemap references in build output #990
Closed
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.
Problem
When a webpage is loaded with DevTools open, the browser automatically attempts to fetch
.map
files if a sourceMappingURL comment is present at the end of each JavaScript file.//# sourceMappingURL=xxx.js.map
Vite includes this comment by default when
build.sourcemap
is set totrue
.In our case, sourcemaps are removed after the build process by the Sentry plugin, so these requests result in a large number of 404s and can cause performance issues.
Solution
Set
build.sourcemap
to'hidden'
invite.config.ts
.https://vite.dev/config/build-options.html#build-sourcemap
This ensures that sourcemaps are still generated, but the sourceMappingURL comment is no longer injected into the final JS output — preventing unnecessary network requests triggered by DevTools.