feat(rollup-plugin): enable sourcemap output for css modules #4852
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.
Thought it would be nice to have sourcemaps work all the way through to production so I updated our rollup plugin to emit sourcemaps 👀
Sourcemaps are generated as files that are siblings to generated
*.css
files. ThesourceMappingURL
should be only a name pointing to the*.css.map
file of the same name in the same directory as the generated*.css
file.Changelog
New
Changed
Removed
Rollout strategy
Testing & Reviewing
sourceMappingURL
between CSS and sourcemap is correctAlternatively, you can use the
app router
example to test out that sourcemaps are generated correctly