-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Builder-Vite: Fix Turbosnap #30522
Builder-Vite: Fix Turbosnap #30522
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.
LGTM
3 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile
View your CI Pipeline Execution ↗ for commit 473e1b9.
☁️ Nx Cloud last updated this comment at |
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 feel like the proper fix would have been to keep the slash out, but add it in the preview-stats plugin instead. But I'm fine with this due to time.
Logic in |
Builder-Vite: Fix turbosnap (cherry picked from commit a019db8)
@valentinpalkovic @JReinhold is the goal to remove that slash? If so, we can add that as an entrypoint for TurboSnap: chromaui/chromatic-cli#1155 |
Thanks @codykaup. That definitely helps! I will keep the code though for backwards compatibility |
Should I go ahead with that change or are we good with keeping the slash? |
Looking forward it would be good to get rid of the slash so please go ahead with your PR. In the future, Storybook will also remove the leading |
Closes #30521
What I did
Re-added the slash after
virtual:
for some virtual ids to not break Chromatic's TurbosnapChecklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal
,ci:merged
orci:daily
GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli-storybook/src/sandbox-templates.ts
Make sure this PR contains one of the labels below:
Available labels
bug
: Internal changes that fixes incorrect behavior.maintenance
: User-facing maintenance tasks.dependencies
: Upgrading (sometimes downgrading) dependencies.build
: Internal-facing build tooling & test updates. Will not show up in release changelog.cleanup
: Minor cleanup style change. Will not show up in release changelog.documentation
: Documentation only changes. Will not show up in release changelog.feature request
: Introducing a new feature.BREAKING CHANGE
: Changes that break compatibility in some way with current major version.other
: Changes that don't fit in the above categories.🦋 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/core
team 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>
Greptile Summary
Based on the provided files and context, I'll provide a concise summary of the changes:
Fixed TurboSnap functionality in the Vite builder by modifying virtual module path handling in development mode.
code/builders/builder-vite/src/transform-iframe-html.ts
to include forward slashcode/builders/builder-vite/input/iframe.html
for proper virtual module resolutioncode/builders/builder-vite/src/virtual-file-names.ts
with consistent forward slash usageThe changes are focused on path resolution for virtual modules to ensure proper functionality of TurboSnap in the Vite builder.