I have been experimenting for a couple of years using decoupled storybook. This means installing storybook in a seperate part of a mono-repo or it means installing it outside of the project repo / directory.
Advantages:
- Doesn’t pollute or create incompatibilities with the main FE repo, is completely seperate
- Can be used with or without permission from the project owner. You can use it as you would any other tool like an IDE.
- Less coupling between the existing project and the storybook implementation. More future proof.
Disadvantages
- for example Vite, you will need to maintain 2 copies of vite configs and also match all deps in the decoupled directory
Dicussion with Cursor IDE (likely claude 3.7) about
- pulling in all fe deps via yarn workspace. cons is it might pull in things we don’t need and we are not really testing the components in isolation
- using turbo or nx for multi config across mono-repos This didn’t really lead to anything because it is more about having partials based package.json deps that could be assembled based on functionality, but there really isn’t a simple solution for this. maybe future-work