Update storybook to 5.3 #2618
Merged
Update storybook to 5.3 #2618
Conversation
This file contains hidden or 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
|
💦 Potential splash zone of changes introduced to No significant changes to This comment automatically updates as changes are made to this pull request. |
kaelig
approved these changes
Jan 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
WHY are these changes introduced?
Keeping up to date, setting the stage for potential docs integration at a later date.
WHAT is this pull request doing?
Updates storybook to 5.3.2
Updates chromatic to 3.4.1
Performs migrations as per https://github.com/storybookjs/storybook/blob/next/MIGRATION.md. Most notably migrate to use the new config layout where presets, story listings, manager config and webpack config are all in a single file.
How to 🎩
Run storybook locally and see it all works
View uploaded stories and see they are all the same
Test hot reloading by editing the Playground / component code (both js and scss) / a component readme and see that they update without requiring a refresh