Gert Hengeveld ⚡

@Matt0xley @mrdoob Reads like AI

@mrdoob The commit messages are something else 🤣

Someone made a PR aiming to remove vulgar words from the project 🙃

Storybook Test sneak peek 👀 ⚡️ Blazing fast tests that run in the browser 🌈 Component, visual, and a11y tests simultaneously 🚦 Visualize results inside Storybook 👉 Click-to-debug in your own browser 🌐 Optimized for test coverage 💻 VSCode integration via Vitest

@chadbr @BenjaminKomen @storybookjs github.com/lukeed/polka Polka is the smallest lib that solves the need of a basic server+router+middlewares. It's mature and stable. The e18e community recommended it. Been used in SvelteKit from day 1 and Vite are considering migrating over.

@GHengeveld @BenjaminKomen @storybookjs Polka?

Is @storybookjs bloated? Not anymore.

@wollantine @storybookjs Thanks! I'm glad to have a discussion on this platform that doesn't end in a flamewar for once 😅

@GHengeveld @storybookjs Thank you, and thanks for listening to me, even though our visions are not aligned.

@wollantine @storybookjs Sorry, I don't think X is the best place to explain the rationale behind API designs. You seem you be opinionated and have a good understanding of Storybook, so I invite you to speak up on Discord. There's RFCs and discussions behind every decision, and you are free to take part.

@GHengeveld @storybookjs What??

@wollantine @storybookjs We are always walking a fine line between flexibility and locking things down. We want customizability but also want to continue to evolve Storybook in the future without having to do breaking changes. That's why most APIs are purpose-built rather than "anything goes".

@wollantine @storybookjs Freedom is a footgun, unfortunately. The problem with providing absolute control is that people will use this freedom to make all sorts of customizations, only to complain when those customizations break with the next update. Absolute freedom doesn't play well with semver.

@wollantine @storybookjs Storybook is neither a library nor a framework, it's a dev tool. We are however working on some changes that allow you to customize your Storybook to focus on a certain use case, such as docs or testing. Tags will have a big role to play there.

@GHengeveld @storybookjs Storybook was meant to be a helper library, not a framework.

@wollantine @storybookjs The challenge we have is that people use Storybook for various use cases. Some want a lightweight component playground, while others want extensive docs features and others are building their whole app inside of Storybook and therefore need testing tools for complex components.

@GHengeveld @storybookjs I think storybook has lost sight of what it should be. Just give me a server, a configurable sidebar and navbar components, mdx support and a couple more components (canvas, code block, args picker, icon, typography and color galleries, actions/logs view), and that's all we need.

@joedzado @storybookjs That's what @NorbertdeLangen does most of the time.

@GHengeveld @storybookjs My favorite diffs to write are deletes.

@erikras I would return an object rather than an array, but you do you.

Let's play: RATE!!!! MY!!! API!!! Lately I'm really loving the "hook that returns a component" pattern. Tell me why I'm wrong.

@nathankurtyka @storybookjs Run `npx storybook@latest init` and pick `html` as project type:

@GHengeveld @storybookjs How can Storybook be used for a vanilla JS project?

@t3dotgg @storybookjs Awesome. You might even become a convert one day. We're trying.

@GHengeveld @storybookjs As a chronic Storybook hater, this is really good to see and makes me more hopeful

@l0gicgate @storybookjs Wow, version 5 is a blast from the past. Hard to even compare it to v8.

@GHengeveld @storybookjs The last time I used it was v5. Just bootstrapped v8 at work this week and it was incredibly easy compared to previous iterations. Well done 👏🏼

@wollantine @storybookjs Please elaborate. What about the CSF syntax makes it bloated? CSF 3 is pretty nimble, much less boilerplatey than CSF 2 was.

@GHengeveld @storybookjs Stories are now, though.

@BenjaminKomen @storybookjs Deduping dependencies (e.g. Babel was included multiple times), replacing dependencies with more nimble alternatives (e.g. Express -> Polka), among other things.

@GHengeveld @storybookjs Interesting, what was your approach to reduce dependencies? Write some code yourself instead of relying on a package?

@storybookjs There’s a longer demo video here: github.com/storybookjs/st…

Sneak peek: Run component tests directly in Storybook s/o to @GHengeveld

@markozxuu @domyen @storybookjs If you really can’t wait, the work is happening right here: github.com/storybookjs/st… There’s a canary release on there.

@domyen @storybookjs @GHengeveld Thank you, Dominic ❤️

Storybook 8.3! ⚡️ First-class Vitest integration to run stories as component tests 🔼 Next.js-Vite framework for Vitest compatibility & better DX 🗜️ Reduced bundle size for a 30% smaller install 🌐 Story globals API to standardize stories for themes, viewports, and locales 👇