Bundle Size
See original GitHub issueProgress
Bare | 1.0.0 | 1.0.3 | |
---|---|---|---|
Size | 90kB | 1.1MB | 381kB |
Original Issue
As a test, I integrated the (very minimal) CSS we use in react-resizable
for use with styled-components
.
https://github.com/STRML/react-resizable/tree/styled-components
This increases the bundle size from 90kB to 1.1MB.
Is this intended for use in libraries, or is its goal more toward application use with an eventual extraction step to keep it out of the runtime?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:8
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Bundlephobia | Size of npm dependencies
Bundlephobia helps you find the performance impact of npm packages. Find the size of any javascript package and its effect on your frontend...
Read more >Slimming down your bundle size - LogRocket Blog
A critical part for improving frontend performance is to reduce the JavaScript bundle size that should be downloaded via the network.
Read more >bundlejs - Online bundler + npm package bundle size checker
A quick and easy way to bundle, minify, and compress (gzip and brotli) your ts, js, jsx and npm projects all online, with...
Read more >5 Methods to Reduce JavaScript Bundle Size - Bits and Pieces
4. Compressing Bundles. If your application bundle size increases and affects performance, you can compress them to reduce the size. Gzip and ...
Read more >Analyze your React app's bundle size and reduce it using ...
As your React app gets larger, you may have to start worrying about its bundle size. An app's bundle size is the amount...
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
As of 1.0.6 with #96, we’ve gotten an even smaller UMD build and a huge parsing performance jump!
Current status of the UMD build:
Can’t see any quick wins anymore, I think this is as small as we can go right now, so I’ll close this for now. 50% is PostCSS, let’s see if #59 can do something about that!