-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Add warning and example how to pass arguments to Cypress when using npm run script #1418
Comments
I think for something like
|
@bahmutov I would like to work on this, if this is still up for grabs |
@nupurgrover Yes! Is still available. |
Great! I'll submit a PR |
I could do this if its still needed @jennifer-shehane |
@bhayward93 Yes, feel free to pick up. |
I see this problem pretty often: user is trying to
npm run cy:run --record ...
without separating arguments with--
(should benpm run cy:run -- --record ...
)We need to put this warning in several places, because people not familiar with NPM's quirks will get stuck and frustrated. I see a couple of places where this warning could be added
In the existing https://docs.cypress.io/guides/guides/command-line.html#How-to-run-commands warning, we need to stress this point by adding "important"
It would be nice to create reusable warning template that we can include on demand, just like @flotwig has done with network stubbing warning in this commit 50c4c71
I have existing NPM run warning here: https://github.com/cypress-io/cypress-documentation/blob/develop/source/guides/guides/command-line.md#how-to-run-commands
Maybe we could have a shorter version of the above warning that can be inserted into more places
The text was updated successfully, but these errors were encountered: