fix(deps): update dependency next-transpile-modules to v10 #37
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 contains the following updates:
^9.1.0->^10.0.0Release Notes
martpie/next-transpile-modules (next-transpile-modules)
v10.0.1Compare Source
v10.0.0Compare Source
Hello everyone! No breaking changes in this version, I just bumped it to make sure people are careful when upgrading to Next.js 13. Please make sure to read the additional notes below regarding the future of
next-transpile-modulesand Turbopack.If you appreciate my work, and if you can afford it, you (or better, your company) can show support by sponsoring me (or just buying me a beer 🙌).
Support for Next.js 13
Enjoy!
Experimental support for the
app/directoryNext.js 13 comes with beta support for the new
app/directory, and next-transpile-modules supports it.Please think twice before using this feature as it's still experimental and
next-transpile-modulescould break at any of Next.js commit.Note on Turbopack
Turbopack being in alpha,
next-transpile-moduleswill not be supporting it. It may work out of the box, it may not, I will not work on it before it's more stable.Note on the future of
next-transpile-modulesandtranspilePackagesNext.js 13 comes with a new option called
transpilePackages. This new experimental feature currently allows to transpile local and npm ES modules, so you might not neednext-transpile-modulesanymore, ifyou're ready to enable experimental features on Next.js.That said, and this is great news, the Next.js team is working on feature parity with
next-transpile-modules, sonext-transpile-moduleswill disappear some day in the future.There is no clear timeline yet, so in the meantime, I'll keep maintaining this plugin until:
transpilePackagesis not experimental anymoretranspilePackageshas feature parity withnext-transpile-modulesThat's it!
Take care of yourselves and happy coding!
Configuration
📅 Schedule: Branch creation - "every weekday after 2:00 am before 6:00 am,every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.