vitro VS cosmos-js

check out this one https://github.com/remorses/vitro

I’ve used storybook for 4 years in teams of 1-15 devs and I’d say it’s a must have for any serious react app with 3+ full time developers. It has its rough edges sure but the ROI is 10x nonetheless in my experiences.

Advantages

- Testing components in isolation forces some good practices and allows to keep the codebase in check by encouraging good practices (limited coupling of unrelated parts of the codebase

- It’s super productive because it is both a form of unit tests, useful during development of UX in « TDD mode », and a very good documentation of your UI components. It greatly reduces the effort needed for both these aspects.

- For DX, the hot reload is generally faster in storybook than in the App (except if you use vite/snowpack in your app, so far..) because reloading a single component is faster than reloading the whole app and its state. In a large CRA our hot reload could sometimes take up 1min in complex cases, while storybook was taking 3s.

- Coupled with Chromatic (their hosted platform) and its GitHub integration it makes QA and visual regression testing a joy, 10x faster than alternatives, I really recommend that.

- It allows to share/iterate easily your ongoing developments with non-tech people in your organisation at early stage. A very good bridge between Figma and the final UI. A good support during Daily meetings about UI, just shared the deployed story url to ask for feedback.

Drawbacks

- It has its own Webpack config. So if you have a custom Webpack config in your app (don’t do that anyway, unless absolutely necessary) then be prepared to duplicate the customizations in your storybook config

- Global React Contexts needs to be duplicated in your storybook config and, if necessary, configured for individual stories. For example if your signup button changes based on an Auth status stored in a global context, then you will have to use Story.parameters to customize the content of the Auth context.

- We had a couple instances where storybook was the limiting factor for us to embrace some new/fancy tech, like yarn v2 or service worker. However maybe that’s a good litmus test: things that storybook support are state of the art JS and generally safe to use. Things that storybook does not support out of the box will cause you problems with other tools anyway: if it’s not storybook, some other tool like Cypress, Jest, Next, or some browsers will cause you trouble with your “shiny new tech”

- It can be slow to startup. We had a storybook with 300+ complex stories and it took 5min to startup and 10min to build in the CI

- It had some API changes/ migration pains a couple years back. However I think the new API is very good and will last a long time so this is behind.

Overall I definitely advocate to use storybook, especially with Chromatic, the ROI is 10x. If you find yourself limited by it in 2021 despite configuring it, maybe question your own tech stack.

Don’t try to implement your own storybook copycat (we had a colleague develop an alternative https://github.com/remorses/vitro , but i think it was not worth the effort)

If you want to see a state of the art repo in NextJS that uses storybook extensively with some customizations, check https://github.com/Labelflow/labelflow/

React Cosmos emerges as an invaluable asset among React debugging tools, tailored for both React and React Native projects. It stands out by offering a conducive environment for developers to meticulously work on, test, and iterate UI components, ensuring they seamlessly integrate with the intended application settings.

I switched to cosmos (https://github.com/react-cosmos/react-cosmos ) awhile back and like it a lot more. Storybook might have caught up this now I havnt tried again since.

4. React Cosmos

There’s react cosmos https://github.com/react-cosmos/react-cosmos

Enter https://reactcosmos.org. It's an alternative to Storybook and to me looks a bit cleaner with smaller amount of boilerplate needed to get running out of the box. It runs a separate dev server with a clean UI displaying all of your component fixtures.

React Cosmos This is a useful developer tool that aids in the creation of reusable React components. It looks for components in React projects and allows them to be rendered using any mix of props, context, and state. React Cosmos allows developers to simulate any external dependency, such as localStorage or API replies, in order to examine the current state of their project in real time. 11.React Sight This React visualization tool provides a visual depiction of the structure of React apps to developers. The tool requires the previously described React Developer Tools for Chrome. Developers who want to use it will also need to install React Sight as a Chrome extension, which adds a new "React Sight" panel to Chrome DevTools. React Router and Redux are supported by the utility. 12.React 360 This is a web-based platform for producing interactive 360-degree experiences. It blends React's declarative capabilities with current APIs like WebGL and WebVR to allow developers to construct applications that can be used on a variety of platforms. The tool is designed to make the creation of cross-platform 360 experiences easier by leveraging web technologies and the robust React ecosystem. Conclusion React has become such a valuable framework for frontend developers who want to create attractive and effective user experiences thanks to these and many other tools. Of all, this is only a small selection of fantastic tools. Every year, the number of React developer tools expands. The React community is dedicated to assisting one another and making React development more developer-friendly.Get assistance from the best react agency to build a mobile application.

react-cosmos - Dev tool for creating reusable React components

5. React Cosmos

React Cosmos is a library that provides a sandbox environment for developing and testing React components in Isolation.