Add flag to disable inline sourcemap comment
See original GitHub issueIn addition to inline comments of the form:
/*# sourceMappingURL={your-file.css.map}*/
,
The sourcemap V3 spec also defines the SourceMap HTTP header https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/SourceMap, which links the location of a file’s accompanying sourcemap.
It would be great to have a compiler flag which disables the inline sourcemap comment, for the case where you wish to generate sourcemaps, but use the HTTP header instead of the inline comment to specify the location of your sourcemaps.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (9 by maintainers)
Top Results From Across the Web
SourceMapDevToolPlugin - webpack
This plugin enables more fine grained control of source map generation. It is also enabled automatically by certain settings of the devtool configuration ......
Read more >Webpack-dev-server doesn't generate source maps
I use babel-loader, but can't figure out how to generate or where find source maps for transpiled files. I tried eval-source-map , inline-source...
Read more >Source Maps - SurviveJS
Inline source maps add the mapping data directly to the generated files. Separate source maps emit the mapping data to separate source map...
Read more >The build Property - Nuxt
Enables CSS Source Map support ... already activated through nuxt.config.js or otherwise, devtools enable regardless of the flag. ... Add webpack plugins.
Read more >source-map-support - npm
If multiple sourceMappingURL comments exist in one file, the last sourceMappingURL comment will be respected (e.g. if a file mentions the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Let me try this. I’ve cherry-picked a commit from https://github.com/less/less.js/issues/3398#issuecomment-501334699 I’ll start checking how tests are written.
@susnet Changed it to “up-for-grabs”