You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all - thank you for your hard work, guys! Really appreciated!
Is your feature request related to a problem? Please describe.
Every time when I do npm install it downloads 17Mb from the NPM registry for @zxing/library - because it contains source map for every single JavaScript file there. Without those MAP files the archive becomes 9Mb.
Describe the solution you'd like
Would you be so kind and remove the MAP files from the distributed package? When I include the library in my project - Webpack will generate new source maps (if I need them at all).
Describe alternatives you've considered
I can write a shell script which will find and delete all MAP files after npm install - but it feels a workaround rather than a clean solution.
The text was updated successfully, but these errors were encountered:
First of all - thank you for your hard work, guys! Really appreciated!
Is your feature request related to a problem? Please describe.
Every time when I do
npm install
it downloads 17Mb from the NPM registry for@zxing/library
- because it contains source map for every single JavaScript file there. Without those MAP files the archive becomes 9Mb.Describe the solution you'd like
Would you be so kind and remove the MAP files from the distributed package? When I include the library in my project - Webpack will generate new source maps (if I need them at all).
Describe alternatives you've considered
I can write a shell script which will find and delete all MAP files after
npm install
- but it feels a workaround rather than a clean solution.The text was updated successfully, but these errors were encountered: