-
Notifications
You must be signed in to change notification settings - Fork 447
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
fix: set strictRequires to auto when building auto updating studios #8367
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
No changes to documentation |
Component Testing Report Updated Jan 24, 2025 11:45 AM (UTC) ❌ Failed Tests (2) -- expand for details
|
⚡️ Editor Performance ReportUpdated Fri, 24 Jan 2025 11:46:45 GMT
Detailed information🏠 Reference resultThe performance result of
🧪 Experiment resultThe performance result of this branch
📚 Glossary
|
Any chance we can get #8364 working first? |
Oh, yes 💯 – would love to see that one merged first |
c802690
to
12b330b
Compare
12b330b
to
d9a518f
Compare
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 for tracking this down 🙏. Looks good to me. I agree with Binoy, it would be good to land #8364 first.
cc @bjoerge @binoy14 |
I think we can merge this instead of waiting for the tests |
Description
When building auto-updating Studios with Vite 6 we ran into an issue caused by the default of
commonjsOptions.strictRequires
that changed fromauto
totrue
between v5 and v6 (mentioned in the advanced section here: https://vite.dev/guide/migration#advanced)This caused the vendorized react bundle to place all named exports on the
default
export instead of exporting them all individually which then broke named imports.This PR explicitly sets
commonjsOptions.strictRequires
toauto
which will produce the same output in both Vite v5 and v6.We mitigated the earlier issue by reverting back to to Vite 5 (#8362). Now that we know the exact cause, and the fix, it would be good to have this merged so we can safely upgrade to Vite 6 again without affecting auto-updating Studios.
Notes for release
n/a –internal