Storybook recently introduced an on-demand architecture for 3x smaller builds and faster load times in the 6.4 release. I won't dive into the data or details. At a high-level, Storybook achieves this performance improvement by loading each story independently rather than packing them into a single monolithic bundle.
Now that we can bundle and lazy-load stories can be independently, I was curious if we could take one more step in optimizing our static story assets. 🤔
Dustin and his team found that using brotli compression for their design system Storybook significantly improved load speeds for teams in Tokyo and Singapore (APAC). This may not be an issue if using a low-latency CDN for your teams Storybook. However, brotli compression is an easy integration that might be worth experimenting! 🧪
Adding brotli compression to our Storybook configuration is made convenient thanks to the to the brotli-webpack-plugin. First, install the plugin package as a dev dependency.
Then, add the plugin to the main.js webpack config for Storybook.
Build a production-ready version of the Storybook. This is usually the build-storybook script when using Storybook's default setup:
The output will include *.(js|css|html|svg) files as usual. With the plugin installed, it should now also generate *.(js|css|html|svg).br assets which will be preferred and served by brotli compatible static servers.
One way we can test the Storybook output is by using http-server static HTTP server with the -b or --brotli flag enabled. Preview it locally by running the following command:
You can verify the brotli encoding in the the Chrome DevTools Network tab.
Subscribe to the newsletter
Be the first to know when I post something new! Thoughts about code, design, startups and other interesting things.