The new react error boundary makes devcards fail spectacularly. I'm tempted to fork it and create an error boundary at each point… That seems wrong though?
I think dev cards is pretty much “done” from the authors perspective but being able to inline hooks, have error boundaries at each card, etc seems good
I wonder what the useful set of features are for such a tool. Seems like storybook is now "best in class", so starting there?
I'd love to know how they manage to support so many libs
Storybook covers a lot of the same functionality yeah
I think it’s a matter of hours spent lol
Storybook is less a library and more an app that you build with some of your code included. I guess similar to dev cards in that regard
It has its own build tool chain though
Storybook doesn’t exactly cover testing, and it’s a PITA even for regular JS projects sometimes because you have to configure both the storybook build and your own builds to work with whatever compile-time transforms, shims, etc. are necessary for your code
What I often wish for for REPL purposes is a way to quickly evaluate a component that will open a new window with controls over state, props
But it’s a PITA with including necessary CSS and other things