.map
assets after app is loaded and rendered?.map
asset (404
error), would there be performance impact? Should I care about fixing it?Note that fixing the last one may not be as easy as serving the .map
assets if there are complicated concat / minify build steps.
Most JavaScript and CSS sources are usually minified and source maps serve as a memory map to the compressed files. It's generally a good practice to minify and combine your assets (Javascript & CSS) when deploying to production.
A “source map” is a special file that connects a minified/uglified version of an asset (CSS or JavaScript) to the original authored version.
Source maps create a map from these compressed asset files back to the source files. This source map allows you to debug and view the source code of your compressed assets, as if you were actually working with the original CSS and Javascript source code.
Firstly: No, there is no necessity for source maps whatsoever. You need not even generate them, unless you want to use them for debugging.
A quick test using Charles Web Proxy shows that source maps are only loaded if developer tools are opened. If you load a page without dev tools opened, there is no http request for source maps.
The behaviour was the same in Chrome 43 and Firefox 38.
So it appears they would be no impact on production environment.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With