Use the latest swc_core, fix compatibility with Next.js 15 #111
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
| Pages will still be broken, next changed the provided filename in the metadata. Plugin can't detect if a file is part of pages router. |
| Thank you for letting me know, I also noticed Next.js is not using the latest version of swc_core in their repo, instead they use 0.106.3 for now https://github.com/vercel/next.js/blob/97153cc838d24c58c13f583f1d88f21b30a8621a/Cargo.toml#L89 PR to update to latest version: vercel/next.js#71683 |
| @remorses Can you update |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
This PR should fix compatibility with Next 15
Fix #110