Skip to content

Percy Storybook config not recognised after updating to Storybook 6.5 #591

Answered by Robdel12
JodiWarren asked this question in Support
Discussion options

You must be logged in to vote

👋🏼 Hey @JodiWarren! This typically happens when the @percy/* packages resolve to slightly different versions (due to weird dependency resolution from npm or yarn). I don't see this warning locally in our example app so I'm guessing that's what's happening here. You can delete your node_modules entirely and see if that fixes it after reinstalling. If not, you can install the SDKs fresh from the command line which should bring the lockfile inline again: npm/yarn -D @percy/cli@latest @percy/storybook@latest

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@JodiWarren
Comment options

Answer selected by JodiWarren
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Support
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #590 on June 21, 2022 17:05.