Reduce npm package size#7
Conversation
|
@ai sorry for slow response I think we should keep webpack, because currently, it is necessary for benchmarking in a browsers. And I like the idea of removing comments from published code. If you think it's safe enough, so let's do it. |
|
And as I understand, it should be major release? I'm fine with it. We can release it as 1.0.0 BTW. I thought that it will be useful to try keep in sync versions with original source-map, but seems that it doesn't make any sense. |
Can we build webpack version just to use in benchmark and do not put file to npm package? |
Yeap, let’s do major (1.0 or 0.7). |
|
😍
|
This change reduces
source-map-jsfootprint innode_modulesfrom 700 KB (!) to 100 KB.Now,
source-map-jsis 77% of installing size of PostCSS 😓.dist/with webpack pre-build. Use case for pre-build is very limited and can be easily replaced bywebpackon user’s side. For instance, most of my open source doesn’t have pre-build files.README.mdin npm package byclean-publish. You will to release this package withnpx clean-publishinstead ofnpm publishAlso #6 can be merged to fix now useless
package.jsonkey,