-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Cypress version #5703
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
Comments
It is also to notice that Cypress Upgrading to Cypress 4 would fix that too. |
+1 For this request. We need cypress ^4.11.0 to have the support of the experimentalShadowDomSupport flag : https://docs.cypress.io/guides/references/experiments.html#Shadow-DOM |
Just looked at current pull-request, it is already a work in progress => #5139 |
It's now in a catch 22 of a new major release of Cypress is coming out soon, because it took so long to approve the PR to upgrade! It would be better if Cypress was a peer dependency, so that we can choose the version we want, and those who need to maintain BC can still do so. |
Oh yes...Good idea.... |
The current version is
Please, can we release it? At least to the I can't use cypress 3 in WSL 1 and WSL 2, while And I can't install this plugin from github, because I use npm, which doesn't support installing from monorepo. Looks like the only way for me is to use npm-force-resolutions. Or, I can switch from npm to yarn, which supports workspaces |
This is not a solution:
Because yarn v1 doesn't support workspaces. And Vue doesn't work with yarn v2 which supports workspaces. |
I tried to use npm-force-resolutions to force cypress newest version is 5.5.0, but it does not work, still stuck in ^3.8.3. |
It definitely worked for me. |
I followed the guidance from npm-force-resolutions, added in package.json "resolutions": { "cypress": "5.5.0" }, "script": { "preinstall": "npx npm-force-resolutions"}, tried the second times but unfortunately, it's not worked. |
What error are you getting? |
Due to cli-plugin-e2e-cypress still use cypress v3.8, I cannot start e2e testing , cy.route2 require cypress v5.x |
Try to remove your |
Great, it works now, thank you. |
It does not work for me.
|
Yeah, I had this one as well, but not sure how to fix it. Perhaps, a different version of plugin or cypress will work. Maybe removing |
Yeah, remove node_modules first, if it still happen, then please provide more information: What command did you run, also what is in your package.json? |
Install rxjs as a dev dependency worked for me |
Hey all, our major release cadence is every 12 weeks. Becoming a peer dependency would be most helpful for us. Vue CLI is in a bind because Cypress releases breaking changes, and Vue CLI does not want to break users' codebases. I'm looking into this failure right now. |
We're gonna discuss with @sodatea tomorrow-ish (specifically, @elevatebart will). I have a non-Vue CLI workaround for those that are interested:
The start-server-and-test package is what we use internally and is built + maintained by a Cypress core member. It's useful for all sorts of stuff, but especially for E2E. |
This is exactly what I have done to decouple Vue cli and cypress. First I create new project using Vue cli with cypress e2e (so that Vue cli creates all the config files for cypress). Then I manually delete Vue cli cypress plugin in package.json and add start-server-and-test as per what @JessicaSachs said above. |
@layanto this is what I do as well. My teammate @dmtrKovalenko has an outstanding |
A temporary workaround shipped: https://github.com/vuejs/vue-cli/releases/tag/v4.5.9 |
Updated in v5.0.0-alpha.0 |
What problem does this feature solve?
Hi. The Cypress version is still on 3.8.3. Can this be upgraded? Thanks!
What does the proposed API look like?
"cypress": "^4.11.0", (I think is the latest version)
The text was updated successfully, but these errors were encountered: