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

npx storybook@latest init
Updated my @storybookjs and @angular using @vite_js post with a much easier setup! Its about as close as you can get until an official integration comes from the Storybook team 🤝 dev.to/brandontroberts/using…
1
7
53
3,049
Storybook retweeted
⚡ Speaker highlight: Yann Braga, Core Maintainer at @storybookjs Storybook is well-known as a one-stop-shop for your components - from development over testing and documentation. Recently, they partnered with @vitest_dev to build the ultimate component testing workflow which includes: 👆 Interaction tests ♿️ Accessibility tests 🖼️ Visual tests 👀 and more @yannbf will give us some insights and show the full power of Storybook x Vitest at ViteConf 2025. 👉 Get your tickets at viteconf.amsterdam/
5
28
14,774
With either technique, you now have a mocked module available in all of your stories. You can manipulate the behavior in the same place where you test it. It’s the perfect balance of simplicity and powerful flexibility.
1
1,011
When you need more control over the mock implementation, use the `__mocks__` convention to provide a mock file:
1
82
You have two options when setting up a mock, automatic or with a mock file. For most cases, the automatically created mocks are perfect. Just call the `sb.mock` utility in your Storybook's preview configuration.
1
92
Testing components that depend on things like localStorage or authentication can be tricky. Storybook makes it easy with our new module mocking API built on top of @vitest_dev's excellent mocking tools.
1
6
24
1,600
AI-generated UI ≠ production UI. AI UI is off-brand without your design system, and falls apart in production. Join us live with @tpitre, CEO of Southleft & AI-powered DS expert, to see how Storybook + MCP + Claude generate UI from your real components. Register in comments👇
2
6
18
1,551
Published the vitest-plugin-rsc package to npm with nextjs support!
2
5
12
1,847
Storybook retweeted
👀 Reminder: our webinar’s tomorrow A11y testing isn’t either/or. Automated checks catch the obvious. Manual testing catches the weird stuff. Used together = fewer bugs in prod. Join us + Homer Gaines, CPACC to break down a workflow that scales. 🎫 Register in the link below.
1
1
2
902
Storybook retweeted
Automated a11y tests = fast + scalable. Manual a11y testing = real-world coverage. Used together? You catch more bugs before they ship. Join us + accessibility expert Homer Gaines to build a workflow that works. 🗓️ Tues, Aug 5 — 12PM EDT 🎟️ registration link in comments
1
1
3
842
Have you tried component testing in Storybook yet? We partnered with @vitest_dev to build the best tool for testing your components in the ways that matter. 👆 Interaction tests ♿️ Accessibility tests 🖼️ Visual tests 🛡️ Coverage reports 🚥 Test widget to run tests automatically
1
5
32
1,313
Unit testing RSC, is it possible? Some first success published here: github.com/kasperpeulen/vite…
2
5
31
6,924
Storybook retweeted
.@storybookjs’s accessibility pipeline finally gave me a repeatable a11y flow: review in stories, automated axe checks, keyboard snapshots and visual tests, CI fails on regressions. Feels like a process my team can actually follow storybook.js.org/blog/the-ac…
2
5
1,189
Storybook retweeted
Accessibility debt adds up fast—especially with limited time, lean teams, and legacy code. Join Melanie Sumner (HashiCorp) & Eric Bailey (GitHub) for a live session on how to fix A11y debt without burning out your team or blowing up your roadmap. Registration link in comments👇
1
1
1
914
Storybook retweeted
Accessibility debt piles up fast. Fixing it shouldn’t burn out your team. Join Melanie Sumner (HashiCorp) and Eric Bailey (GitHub) for a live session on how to reduce A11y debt without derailing your workflow or overwhelming your team. 🗓 July 24, 12PM EDT 🔗 link in comments
1
1
3
886