-
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
cypress open yields "bad option: --project" #3254
Comments
Update: re-installing always fixed it before, but now it blows up when running after re-installing.
I have blown cypress away and re-installed several times to no avail. |
Hey @IRCraziestTaxi, what is the name of the root directory where you are running Is there a reason you are using version 3.1.0? We just released version 3.1.5 with lots of bug fixes. |
Could you also open Cypress in debug mode mode and print the logs here? |
Thanks for the reply, @jennifer-shehane.
I am running that command in the root folder of the project where the node_modules folder is located.
No, ProjectName/project-name are what I replaced the actual name of the project using cypress with. So
just means that cypress is running for my project, which I dubbed project-name for this discussion. The only reason I was using 3.1.0 was because that is the version we have pinned in our package.json. I did try upgrading to 3.1.5, but the issue persists...
I will give this debug mode thing a try... how does this work exactly? All the doc says is: On Windows: Then what? Just run |
yes, you then run |
Here is my output after setting debug:
|
Update: I tried a reboot again (after upgrading to 3.1.5) and that seems to have fixed it. Even after verifying I can open cypress and rebooting a second time, it now continues to open. Maybe the upgrade to 3.1.5 did the trick? (And a reboot afterwards, obviously.) Either way, I guess I'll go ahead and close this since it seems to have been an edge case solved by the good old "turning it off and back on". I will try to be careful when opening cypress and note the steps to reproduce the issue in case it comes up again. |
In order to direct better focus on the overall problem that is being described in several issues - we opened one issue to track this behavior #4624 Please add any information about how we can reproduce this bug there. 🙏 |
Current behavior:
Running the command
cypress open
yields outputbad option: --project
; cypress does not start.Note also that I am not providing the
--project
flag; I do not know where that is coming from. I looked at thecypress
andcypress.cmd
files innode_modules
, but I don't see it in there.Note also that completely removing all traces of cypress from my system and doing
npm install
again (which in turns does a fresh install of cypress) fixes it, but I cannot do that every time I need to open cypress; it takes forever.Desired behavior:
Running the command
cypress open
opens cypress.Steps to reproduce: (app code and test code)
node_modules\\.bin\cypress open
. (Cypress will open.)node_modules\\.bin\cypress open
. (Bad option output is yielded.)Versions
Cypress package version: 3.1.0
Cypress binary version: 3.1.0
Edit for full disclosure of command and output:
The text was updated successfully, but these errors were encountered: