-
Notifications
You must be signed in to change notification settings - Fork 3.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
CT + Vite 3.0 does not work with Node >= 17 #23042
Comments
Hey team! Please add your planning poker estimate with ZenHub @astone123 @lmiller1990 @marktnoonan @mike-plummer @rockindahizzy @warrensplayer @ZachJW34 |
The code for this is done in cypress-io/cypress#23048, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior
A Cypress CT project using the new Vite 3.0 support does not work out of the box if the user is using a node version >=17. There is a workaround by explicitly setting the
host
to127.0.0.1
in thevite.config.js
(or the overrides incypress.config.js
), but we should not have to rely on user workarounds.For details, see the vite migration guide regarding dev-server changes.
Desired behavior
Cypress CT projects using Vite 3.0.0 and Node version >=17 should work without user provided workarounds.
Test code to reproduce
nvm install 18
npx init vite
=> I chose a react js appyarn add -D https://cdn.cypress.io/beta/npm/10.4.0/darwin-x64/develop-4d3ad9edaa9b4b19ed10094279f72ed5657b851c/cypress.tgz
(Vite 3.0 hasn't been released yet so I'm using a binary from develop)yarn cypress open
=> walk through CT setupsrc/App.cy.jsx
with contents:Screen.Recording.2022-08-01.at.11.50.55.AM.mov
Cypress Version
10.4.0 (binary from develop)
Other
We did the same change for webpack a while back, so it's makes sense to do it here as well.
#21430
The text was updated successfully, but these errors were encountered: