Looking for ideas for decreasing the webpack bundle Size

decaporg / decap-cms

A Git-based CMS for Static Site Generators

https://decapcms.org

MIT License

17.92k stars 3.04k forks source link

Looking for ideas for decreasing the webpack bundle Size #328

Open bdougie opened 7 years ago

bdougie commented 7 years ago

When you run npm run build you can see the bundle size is ~1.5mb parsed and ~480kb gzipped. I am curious if there are any experts on webpack that help with solutions for decreasing the bundle size.

I don't believe it would be realistic to do so, but I did experiment with Preact and saw a significant decrease in size. I did not explore this fully, but wanted to field this issue to see if anyone has some quick wins.

with preact 👇🏾

peet86 commented 7 years ago

Actually 480kb gzipped is not that bad.. :)

Yes preact is great stuff!
Idea 1: update to webpack 2 and use tree shaking.. it really works.. https://webpack.js.org/guides/tree-shaking/
Idea 2: optimize lodash loading with this webpack plugin and save some kbs. https://github.com/lodash/lodash-webpack-plugin

erquhart commented 7 years ago

Good pointers @peet86 - if you're up for giving either of those a shot it'd be a welcome improvement :)

tech4him1 commented 7 years ago

~~Slightly beside the point here, but wouldn't it be better, if you guys are hosting it on HTTP/2, to bundle the netlify-cms code separately from all its dependencies for caching purposes?~~

EDIT: No longer applicable, as the CMS is not hosted on netlify.com. Plus, some people will use the NPM package directly, instead of a CDN.

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.