-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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
Build breaking when importing JSBI in 13.5.4 #56550
Comments
I was going to create a separate issue for this but seems we're having the same problem. Attaching my repro here: |
Thanks for the quick look @kdy1 |
The cause was a bug related to the new mangling option. I'll fix it soon and will send a PR, hopefully today. The new mangling option was added in #56281 to align with terser |
…8093) **Related issue:** - vercel/next.js#56550
### What? Update SWC crates, to apply bugfixes. ### Why? We adjusted the mangling option to make it identical with `swcMinify: false` with #56281, and it revealed some bugs of the name mangler of the SWC minifier. ### How? - Fixes #56550 - Fixes #56614 - Turbopack counterpart: vercel/turborepo#6171 ### Other Turbopack Changes * vercel/turborepo#6177 <!-- Tim Neutkens - Add support for FreeVarReference::Error --> * vercel/turborepo#6180 <!-- Tobias Koppers - fix chunk loading in build runtime --> * vercel/turborepo#6191 <!-- Justin Ridgewell - Deduplicate referenced_output_assets --> * vercel/turborepo#6171 <!-- Donny/강동윤 - build: Update `swc_core` to `v0.86.1` --> Closes WEB-1775 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Link to the code that reproduces this issue
https://github.com/jeremypress/next-issue-repro
To Reproduce
Relevant code:
This package is linking to UMD via the "browser" entry, which isn't great, but something changed behavior wise between next 13.5.3 and next 13.5.4
Current vs. Expected behavior
Following reproduction steps,
I did not expect this type error
TypeError: Cannot call a class as a function
Verify canary release
Provide environment information
Which area(s) are affected? (Select all that apply)
SWC transpilation
Additional context
I tried to original submit this with a repl, which I think should be a valid way to submit bugs 🤷🏻
WEB-1742
The text was updated successfully, but these errors were encountered: