Skip to content
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

fix(deps): update dependency next-transpile-modules to v10 #37

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 20, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
next-transpile-modules ^9.1.0 -> ^10.0.0 age adoption passing confidence

Release Notes

martpie/next-transpile-modules (next-transpile-modules)

v10.0.1

Compare Source

v10.0.0

Compare 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-modules and 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/ directory

Next.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-modules could break at any of Next.js commit.

Note on Turbopack

Turbopack being in alpha, next-transpile-modules will 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-modules and transpilePackages

Next.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 need next-transpile-modules anymore, 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, so next-transpile-modules will disappear some day in the future.

There is no clear timeline yet, so in the meantime, I'll keep maintaining this plugin until:

  • transpilePackages is not experimental anymore
  • transpilePackages has feature parity with next-transpile-modules

That'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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@vercel
Copy link

vercel bot commented Dec 20, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
opencollective-frontend-template ✅ Ready (Inspect) Visit Preview Dec 20, 2022 at 11:01AM (UTC)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants