We have our own UI library, which means we are responsible for documenting the APIs of these components.
See and browse visual examples of components
Prevent layout issues by assessing the impact of changes to components visually
Storybook seems to be the most popular library for this. However, it does not yet support pnpm (although the alpha does).
To do:
[ ] Explore alternatives. Is there a cleaner, more modern, pnpm compatible alternative? How does it manage commonly used state? E.g.: do you have to wrap all data examples it in a Store.ContextProvider, or is there a common layout you can re-use?
[ ] Storybook. By far the most popular, so tried and tested. Will feel familiar to most. But a bit slow / bulky.
[ ] Ladle. By Uber, drop in replacement for Storybook. Faster, which is nice especially during development.
We have our own UI library, which means we are responsible for documenting the APIs of these components.
Storybook seems to be the most popular library for this. However, it does not yet support pnpm (although the alpha does).
To do:
Store.ContextProvider, or is there a common layout you can re-use?Button,Card,Detail, more?)