refactor: ♻️ storybook with csf3 #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I got storybook running smoothly using the
@storybook/nextjsframework instead ofvite. This way there are less dependancies and the/.storybook/main.tsis a little cleaner.With Storybook v7, how you were using the
@storybook/addon-docsin mdx isn't the recommended way from storybook anymore. instead they prefer to use the new CSF3 format in.stories.tsfiles. These are also less likely to conflict with other MDX compilers like contentlayer which is used in the app/www.For the time being i've just converted the
.stories.mdxto.stories.tsxand not made too many changes (just some arg spreading), but will probably have a look and see if the structure can be improved or if things can be made a little more generic