Industry standard frontend workshop. Develop, test, and document components with ease. Open-source & maintained by @chromaticcom

npx storybook@latest init
Storybook 10 (now in beta) is ESM-only. Our latest post explains why. 🤏 Smaller package size (15%) 🫧 Cleaner, simpler codebase 📉 Reduced bugs from module duplication and aliasing 🧱 A more future-proof foundation for Storybook and its ecosystem
5
6
28
1,961
Storybook retweeted
Thrilled to talk accessibility in Boston tomorrow at Squiggle Conf. In the area? I'd love to meet you!
1
2
982
3
29
1,704
Storybook retweeted
Literally
The next version of Storybook will only have one significant breaking change: Storybook 10 is ESM-only.
1
7
1,757
We've been doing a lot of research and experiments with AI and agent-based development lately at @storybookjs , and we're finally ready to share some of our learnings and prototypes! We have not one but TWO RFCs that we'd love feedback and input on! 👇
1
3
7
4,110
Wonder how Storybook is thinking about AI? Check these RFCs!
We've been doing a lot of research and experiments with AI and agent-based development lately at @storybookjs , and we're finally ready to share some of our learnings and prototypes! We have not one but TWO RFCs that we'd love feedback and input on! 👇
10
2,406
Love this! ❤️ CJS deprecation in JavaScript ecosystem is long overdue. Now Storybook joins as a great example of modern tooling. MSW 3.0 will be ESM-only, too, btw.
The next version of Storybook will only have one significant breaking change: Storybook 10 is ESM-only.
7
8
219
16,454
Goodbye and good riddance. Grateful for where it got us. Happy to bury CJS 6 feet under.
The next version of Storybook will only have one significant breaking change: Storybook 10 is ESM-only.
8
13
606
62,058
The next version of Storybook will only have one significant breaking change: Storybook 10 is ESM-only.
12
54
620
129,303
We're excited about this smaller, simpler, and more modern version of Storybook. You can try it today, in Storybook 10 beta. Check our migration guide for details: storybook.js.org/docs/10/rel…
1
17
3,799
Btw, we've confirmed that Storybook is unaffected by yesterday's security concern and that it is *safe* to upgrade your projects.
🚨 Security alert 🚨 Today, malicious versions of `chalk` and several other packages were published to npm. We've assessed the impact to our users and believe the threat from Storybook specifically is minimal. Sharing for visibility. Stay safe folks! aikido.dev/blog/npm-debug-an…
1
16
4,558
🚨 Security alert 🚨 Today, malicious versions of `chalk` and several other packages were published to npm. We've assessed the impact to our users and believe the threat from Storybook specifically is minimal. Sharing for visibility. Stay safe folks! aikido.dev/blog/npm-debug-an…
1
12
23
8,105
Tips: - check for malware in your project's dependency tree - check the various deps using `npm ls` or similar - clear your browser cache since threat is in-browser github.com/chalk/chalk/issue…
2
1,015
How do you ship React apps across phones, browsers, TVs & even AR/VR? Find out in the closing panel with leaders from @AmazonAppDev, @expo, @storybookjs & @Microsoft: @chris_trag, @kadikraman, @Danny_H_W, @gorhom, Khalef Hosany. Are you joining us? 🎟️ clstk.com/45JsR3V
1
3
17
6,070
Storybook retweeted
A11y lags behind because testing doesn’t match how we build software. Why? - Audits live outside the dev workflow - Page-level tests create noise - CI/CD gets blocked by a ton of old issues Join me at SquiggleConf to build an a11y pipeline using Storybook
1
1
4
940
Thursday: @tpitre (CEO, Southleft) shows what happens when you give AI your design system: ⚡ On-brand UI from the first prompt 🧩 Storybook + MCP + Claude workflows 🚀 Faster prototyping, fewer re-prompts Don’t miss it! (link in comments)
2
2
6
948