Welcome!

I’m thinking about trying to co-locate stories instead, but would that even help if the mock bootstrap needs to happen in the preview.tsx of the storybook app either way? Or is there a way to init the sb.mock _elsewhere_ co-located to the production code?

But when mocking I need to export them from the module and make sure to export the correct _file_ without any accidental barrel intermediates - that has bit me a a few times. The exports block in our package.json’s are also growing in a way I don’t like - and it feels like I’m exporting internals.

Components under test are often pulling their data with retrieving hooks that needs to be mocked. Sometimes these hooks are deeply nested and ideally I want to wrap any complexities with a data-hook next to the component.

Like it! But I'm also a lite bit spoiled because I don't really remember what it replaces :)

The thing I'm struggling with is our monorepo approach. We have not co-located stories but have a separate storybook app with stories for multiple apps and libraries…

Is this new new for 10 or the one we've been using with sb 9.x since summer?

Cool! I've been using tanstack-form with valibot schemas and been pretty happy with that. How does this compare to that?

Upgraded from 8.x just now. Love the visual cue for what's excluded in simulations in the schematic editor!