CLI: Add Visual Tests addon to init
#25850
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
shilman
changed the title
shilman
changed the title
init
tmeasday
force-pushed
the
shilman/add-chromatic-addon
branch
from
d9d3c36
to
8613c3c
Compare
ndelangen
reviewed
Feb 1, 2024
ndelangen
approved these changes
Feb 1, 2024
shilman
force-pushed
the
shilman/add-chromatic-addon
branch
from
b211442
to
d4e4a12
Compare
9 tasks
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.
Closes #25831
What I did
This change to the CLI installs Chromatic's Visual Test Addon by default in new projects:
For users who want to opt-out, there is a one-click uninstall button in the addon's UI. You can also remove the addon with
npx storybook remove @chromatic-com/storybookor by manually deleting it frompackage.jsonand.storybook/main.js.Checklist for Contributors
Testing
Uninstallbutton and verify that the addon is removed🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/coreteam here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>