4 ms·
I love Cosmos! We used to use storybook a few years back but it required ongoing maintenance whenever we made changes to our build configs which meant it would
by root_axis 6y ago
I love Cosmos! We used to use storybook a few years back but it required ongoing maintenance whenever we made changes to our build configs which meant it would slowly fall behind the rest of our application over time. The brilliance of Cosmos is that it relies on your existing configs to build the components, so it's just a "set it and forget it" setup. Being able to produce static builds is also great and we rely on this to generate component previews in our CI so that QA can review component appearance and behavior before we even merge them into development. The Cosmos UI hooks are also a clever use of hooks that allow the fixtures to be tested by non-technical people in a manner that aligns with the logical boundaries of the component's design from an engineering perspective. The approach to designating a fixture file using the .fixture extension is also low effort meaning engineers actually do it. It's awesome, I highly recommend it if you work on a complex react front-end with many individual components.