Percy Storybook config not recognised after updating to Storybook 6.5 #591
-
The problemAfter updating to Storybook 6.5, the Percy CLI seems to no longer pick up the extended Percy config properly. Running
I've isolated this regression to have occured when we updated from Storybook 6.4.14 to 6.5.9. There were a few other Storybook-specific changes made as part of this update, but reverting them does not seem to affect the problem. Environment
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
👋🏼 Hey @JodiWarren! This typically happens when the |
Beta Was this translation helpful? Give feedback.
👋🏼 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 yournode_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