-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
Build issue: "Cannot redefine property: File" with Node.js 20.6.0 #14299
Comments
Ok I see that the issue is already in Babel babel/babel#15927 |
Yeah it is an upstream issue in node, there's not much we can do so closing for now. It's affecting many other projects so hope it should be fixed soon. |
It looks like CI is failing due to an issue with Babel.js conflicting with Node 20.6: babel/babel#15927 vitejs/vite#14299 For now, let's try pinning Node 20.x to 20.5 until the issue gets fixed in Babel. Comparable `typespec-azure` repo PR: https://github.com/Azure/typespec-azure/pull/3502 Issue https://github.com/Azure/typespec-azure/issues/3504 tracks the work to un-pin the Node version.
…conversation-ui/develop/library/node-b46062a" This reverts commit 23cf329. Vite.js is bugged: vitejs/vite#14299
We added a workaround for this in |
Thanks @nicolo-ribaudo, too bad that the Node fix has been slow to come, appreciate you coming up with a workaround. |
Upgrading NodeJS to 20.6.1 will fix this issue. |
same issue, fix with upgrading Node |
Had the same issue and upgraded to 20.7.0 in order for it to work. |
That fixed the issue to me, thanks ! |
The issue has been resolved! Just updated the Node version from 20.6.0 to 20.7.0 |
Describe the bug
When running vite build in an application that worked fine on Node.js 20, before version 20.6.0 (released yesterday), and without anything else having changed, I now get this build error.
This also happens on a newly created app (see repro) so I suspect that the issue is caused by the Node.js version.
This is the vite.config.js file:
Reproduction
Steps to reproduce
No response
System Info
Used Package Manager
npm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: