We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Seems like the recent babel upgrade in next.js is causing problems if you don't have the matching babel versions on our side
The text was updated successfully, but these errors were encountered:
Seems like running babel-upgrade and using "babel-core": "7.0.0-bridge.0" helps.
babel-upgrade
"babel-core": "7.0.0-bridge.0"
Related:
vercel/next.js#4227 vercel/next.js#4239
Sorry, something went wrong.
@taskr/babel uses babel 6.x
@taskr/babel
Upgrading to "@taskr/babel": "1.1.0-next.1"
"@taskr/babel": "1.1.0-next.1"
@usehenri/react should have pinned packages version.
@usehenri/react
Fixed in 08bc7ed
No branches or pull requests
Seems like the recent babel upgrade in next.js is causing problems if you don't have the matching babel versions on our side
The text was updated successfully, but these errors were encountered: