-
Notifications
You must be signed in to change notification settings - Fork 4
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
migrate to swc 3.0.0 for next upgrade #196
Conversation
CodSpeed Performance ReportMerging #196 will not alter performanceComparing Summary
|
As a side note, I’m going to upgrade swc_core of next to v4 and it will be incompatible with v3 of swc_core. There was important perf improvement, and it was a Wasm-breaking change |
good to know - we will upgrade once SWC 4 lands in next.js |
vercel/next.js#71683 is merged. |
thanks @kdy1 for all these insights - is this already part of nextjs |
Co-authored-by: Luca Schneider <[email protected]>
Co-authored-by: Luca Schneider <[email protected]>
🦋 Changeset detectedLatest commit: b8df2df The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
# Conflicts: # packages/yak-swc/yak_swc/src/utils/css_prop.rs # pnpm-lock.yaml
78d6aad
to
ccd1750
Compare
Update the SWC plugin and related dependencies for compatibility with Next.js 15
Version Updates
Implementation Changes
Fold
toPass
API as per SWC's new visitor patternas_folder
withvisit_mut_pass
Pass
traitBreaking Changes Handled
Program.apply()
andFold
Next 15 async
Closes #181
Special thanks to @kdy1 for: