In my current project we use rollbar-sourcemap-webpack-plugin, this plugin generate and upload .js.map files on build process. All .js.map files is recommended to no be public:
I believe this is a common pattern and other projects should have the same problem
Workaround
For now before of npm run deploy we running rm -R dist/js/*.map but I believe this should be the responsibility of the deploy tool.
Solution
Add another optional config (ignoreMatch) to permit ignore some files based on Globbing patterns.
I think this config should be as default something like !**/*.map, but to not generate break change, suggest the default as an empty string for now.
Motivation
In my current project we use rollbar-sourcemap-webpack-plugin, this plugin generate and upload .js.map files on build process. All .js.map files is recommended to no be public:
I believe this is a common pattern and other projects should have the same problem
Workaround
For now before of
npm run deploy
we runningrm -R dist/js/*.map
but I believe this should be the responsibility of the deploy tool.Solution
Add another optional config (
ignoreMatch
) to permit ignore some files based on Globbing patterns. I think this config should be as default something like!**/*.map
, but to not generate break change, suggest the default as an empty string for now.