New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Turbosnap not trigger on dependency update #927
Comments
@Ankoge could you reach out to our support chat so we can dig a little deeper? |
HI @Ankoge I am currently struggling with similar issues (and already contacted the support)... My observation is, that I have troubles with multiple package.json files in the same repo. I can configure base-urls/config-urls etc. whatever I want, but only changes to the package.json in the root directory of the repo trigger dependency-changes... Unfortunately all my code/storybook/chromatic is some levels deeper in the file tree. I can update you if you have more info. @cgbl-90 if you have further ideas, I'd be glad (well, taking a look at your name I assume I am writing with you over the support :D) |
@Ankoge i hope i don't hijack your thread, but just adding some details on the things i discovered (possibly they fit to your troubles)... I enabled the
(Context: the one package.json taken seems to be that in the repo root. While the one I really changed and the one I really use is As you can see, it decides that no dependencies were changed (which is, in fact, wrong) and then skips all snapshots. |
Closing since this was moved to support |
We had a dependency update ("@chakra-ui/storybook-addon": "5.1.0") and that update cause an error in all storybook component, but no turbosnap made so the PR got an approve.
The text was updated successfully, but these errors were encountered: