Ladle has been out for 3 months and the community feedback was overwhelming and amazing. Thank you! Some numbers:
- 🎯 20,000 unique visitors on this website.
- ⭐ 1,300+ GitHub stars.
- 🖊️ 10 contributors.
- 💬 100+ folks joined our Discord community.
Today, it's time to graduate Ladle to its first major stable version 1. We've fixed many bugs discovered by early adopters and added some big features as well:
V1 brings the most requested feature - the full access to Vite configuration. When Ladle was released, it was intended as a tool that could replace Storybook. The bundler (Vite) was just an implementation detail and completely hidden away. However, for more advanced setups, you need to customize various aspects of compilation (like Storybook's Webpack). It makes sense to fully expose vite.config.js and embrace Vite first applications as well. Ladle's configuration has been rewritten from the ground up.
Check the new config documentation.
Breaking Changes
- Ladle now loads top-level
vite.config.js/ts/mjsand uses all its options. - All Vite related options from
config.mjsare removed and an error will be thrown, usevite.config.jsinstead. enableFlowoption removed, you can create your own plugin (check our e2e/flow test).- Programmatic API imports changed to
@ladle/react/serveand@ladle/react/build. --outrenamed to--outDirto mimic Vite configuration, added-oalias,outDirmoved to the top-level inconfig.mjs.--porthas an alias-p,portmoved to the top-level inconfig.mjs.vite.config.jscan be customized throughviteConfigand--viteConfig.--base-urlremoved, usebaseinvite.config.js.--openremoved, useserver.openinvite.config.js.--sourcemapremoved, usebuild.sourcemapinvite.config.js.
This makes our internal setup much simpler since we don't need to pass through individual Vite settings - you can now customize all of them without Ladle being in your way.
Next big features?
We are adding MDX support and making it easier to use Ladle for documentation.
