Reduce bundle size?
See original GitHub issueSince 0.3.0
there’s been a jump in the bundle size. Note that a chunk of it can be ignored due to the addition of the @emotion/core
dependency. I feel like the library at its core could be kept minimal and fundamentally about the theme and sx
prop relationship. @theme-ui/components
seems like an obvious one to keep stand-alone, however lately it seems it’s now part of theme-ui
which has definitely also added to the size of the bundle.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Possible ways to reduce your webpack bundle size - Medium
Here are some cool ways you can reduce your webpack bundle size: ... This will significantly reduce your bundle size. How do I...
Read more >3 ways to reduce webpack bundle size - Jakob Lind
3 ways to reduce webpack bundle size · Easy: Run webpack in production mode · Medium: use an analyzer tool such as webpack-bundle-analyzer...
Read more >How to Slim Down Your Bundle Size
Consider rewriting libraries that are large in size where you might not need all of its functionalities. · Check to see if you...
Read more >Minimizing Webpack bundle size - Anvil
Learn how to minimize your Webpack bundle size by following these best practices, ensuring an optimal user experience.
Read more >Reduce bundle size | Framer for Developers
When measuring the gzipped and minified size of Framer Motion using a bundle analysis website like Bundlephobia, you might see big numbers like...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, this could definitely use better documentation – I think starting with the packages README.md would be a good place
I think any of the packages available will follow semver and should be safe to use their public APIs. The core package was split off based on dependencies, and I don’t imagine there will be a ton of breaking changes there