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
No longer works with next.js 11 #8
Comments
@fabb did you find a fix or alternative? |
I removed the plugin and duplicated the babel config for every application. |
Hey folks. I'm no longer maintaining this plugin, but PRs are most welcome! |
@josephluck what do you use yourself instead? maybe you could add a hint to the readme that next.js 11 is no longer supported? |
I'm no longer actively working with NextJS.
Good shout! |
I've fixed the issue, added tests and created a PR. Hope that helps. |
@rutzfutz - thank you! Published @1.0.5 https://www.npmjs.com/package/next-plugin-custom-babel-config |
Thanks @rutzfutz! |
Most welcome! My thanks go to @fabb for analyzing the change that caused this bug. |
By the way, @josephluck - the NPM package description for 1.0.5 still states "This plugin doesn't work with Next 11. PRs welcome!", which isn't true anymore. |
Does not work anymore with next.js 11 because the loader is no longer called
'next-babel-loader'
but'/absolute/path/to/project/node_modules/next/dist/build/babel/loader/index.js'
.I guess this is related to next.js 11 having inlined the babel loader and others: vercel/next.js#20598
The text was updated successfully, but these errors were encountered: