-
Notifications
You must be signed in to change notification settings - Fork 27.6k
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
Babel error when using override of TypeScript 4.3.2 #27124
Comments
I ran into this as well. Is there a way to set the Babel dependency version in package.json (I'm using |
I'm having the same issue. Tried installing |
Hi, this should be fixed in the latest canary of Next.js |
Hi @ijjk, I tested it and it's working, thanks. |
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
What version of Next.js are you using?
11.0.1
What version of Node.js are you using?
14.16.0
What browser are you using?
Chrome
What operating system are you using?
Windows
How are you deploying your application?
next dev
Describe the Bug
I noticed that the
basic-feature
of docs has the wrong information as it says:It is highly recommended to be on at least v4.3.2 of TypeScript to experience the best performance when leveraging this feature.
But Next.JS still doesn't support some features of the version because of the Babel version 7.12.5, and what's new in TypeScript 4.3 is only added in version 7.14.0 as per the update notes
Uncaught at getBabelError
Expected Behavior
update the Babel dependency of Next.JS to version 7.14.0, or remove the Incremental type checking from the docs telling to use a TypeScript version that Next.JS is not yet supported.
To Reproduce
an example error is using the new TypeScript override:
The text was updated successfully, but these errors were encountered: