-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
fix(build): add module condition in package exports #10036
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
Conversation
@yyx990803 apologies for not creating the issue for this yet, it's still on my TODO list. Do you still need the issue now? I will test ASAP and report back in a bit. |
@yyx990803 I finally found time to do the test, and I can confirm that this works in my case! |
248bcf6
to
3f5fbf6
Compare
Size ReportBundles
Usages
|
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
Just to confirm: This works in the new release. Thanks @yyx990803 ! |
Sorry for delay, the fix does not work for me @yyx990803
The commit bump vue from 3.4.8 to 3.4.13, with nothing else. I am still meeting:
|
/cc @danielroe #9977 has caused a number of regressions with different causes: #10012, #10020, also got another private report from @lehni in his project.
It seems I merged it to soon and it was indeed risky in a patch. For now I have reverted the exports conditions in 7bd4e90 to avoid other unknown regressions.
This PR fixes #10012, but I need further confirmation for the other two cases. @Mister-Hope / @lehni would appreciate if you can try this commit in your project to see if it fixes your issue.
I am also not sure if the addition of
module
would intefere with the bundle size gain in Nitro / Nuxt.