-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
UI: Enable TurboSnap for UI Storybook #19767
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Reuben!
We need to change the CircleCI config though, as it doesn't contain any Git history. From the CLI output:
Retrieving git information
⚠ TurboSnap disabled due to missing git history
Could not retrieve changed files since baseline commit(s).
This typically happens after rebasing, force pushing, or when running against an ephemeral merge commit.
ℹ Read more at https://www.chromatic.com/docs/turbosnap#how-it-works
Maybe you can reach out to Chromatic Support and get this resolved? 🤣
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.
I've updated the depth to 5 for the If that does not work, we may want to consider altering this job to utilize the CIrcleCI helper |
Socket Security Pull Request ReportDependency issues detected. If you merge this pull request, you will not be alerted to the instances of these issues again. 😵💫 Bin script confusionThis package has multiple bin scripts with the same name. This can cause non-deterministic behavior when installing or could be a sign of a supply chain attack Consider removing one of the conflicting packages. Packages should only export bin scripts with their name
Pull request report summary
Bot CommandsTo ignore an alert, reply with a comment starting with
Powered by socket.dev |
@JReinhold @tmeasday Yet, the build in Chromatic clearly indicates that TurboSnap was successful and skipped snapshots as intended. I ran Chromatic locally and it appears that TurboSnap is working correctly.
The change runs correctly on I've modified the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is good, with a few tweaks.
It's interesting that the CI process indicates that TurboSnap was disabled because we could not find the git history
I think the message here is a little confusing, the issue is that snapshotting is entirely disabled for the storybook-blocks
SB right now: https://www.chromatic.com/manage?appId=63591cc9eaf4e8caec2bb5e9
Yet, the build in Chromatic clearly indicates that TurboSnap was successful and skipped snapshots as intended.
You're mixing the two SBs that are tested in that command up, that's the storybook-ui
SB which is working fine it seems.
The change runs correctly on storybook:ui however, not for the chromatic-sandboxes job
I've modified the chromatic.ts task and added --only-changed to see if this might resolve the issue
This is a bit trickier, as we would have to inject the vite config into each sandbox. It can be done, but we are looking to heavily reduce the number of sandboxes we run soon anyway. Otherwise we can take a task to do this on the SB team next cycle.
Yeah sorry for the confusion @ethriel3695
|
@JReinhold you might want to change the
Well, hmm. They are in the same git repo. So they will have git changes. But because of the way they are built I don't think TS will work, as all the file changes will be in @ethriel3695 as I mentioned we are reducing the number of sandboxes we run by 2-3x currently, FYI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good! 💪
I don't know why CI is failing though, some weird Chromatic CLI error.
Could be because you updated the Chromatic version?
Could you try merging next
in and see if that fixed it?
Let me know if |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙌
Issue:
Storybook is using up quite a bit of its story allotment within Chromatic.
We use Vite to build Storybook, which does not work out of the box with the Chromatic feature
TurboSnap
Add a package to allow the Storybook monorepo to use
TurboSnap
What I did
vite-plugin-turbosnap
main.ts
Storybook config file to include the packageHow to test
If your answer is yes to any of these, please make sure to include it in your PR.