-
-
Notifications
You must be signed in to change notification settings - Fork 4
Description
Storybook has been disappointing:
- It's currently simply too slow. This is presumably a combination of:
- Lots of Shadcn components in our code base
- An expensive set of Storybook decorators (maybe it's worth seeing what happens if these are gone)
- Svelte in general?
- It seems to break (due to HMR or similar) more often than a real svelte app
Original PR (no issue).
We documented in our team meeting doc:
careful it might be more effort than it’s worth for replacing a basic sandbox approach and component tests
Yeah...I probably wasn't careful enough.
Is there a tantalizing alternative? We are trying to cover 2 things:
1) A sandbox for (primarily?) manually testing components and their states
It would be pretty easy and cheap to just extend our rudimentary sandbox page with more routes for individual components.
Than would save us the headache off introducing and learning a new dependency.
But, are there any killer features something like KitBook would get us?
The value of Storybook's e.g. viewport emulation tools are seemingly negligeable for us.
2) A component testing strategy
Does KitBook cover this?
Or do we just use raw vitest with its Playwright support?