You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, within my project, to install packages, I must include the --force flag to ensure NPM installs despite some of my dependencies having version compatibility issues. By adding a new key within the cypress step called install_flags, you could allow users to enter any flags to go along with the npm install.
This is useful for my project and potentially many others because some larger projects may contain version dependency errors, and in our case, our app works perfectly fine despite those conflics.
We plan to include Cypress testing within Github actions, but every time the test starts, it fails simply because it fails to install all the required NPM packages within the project.
Image of error occurring in Github actions:
Other
No response
The text was updated successfully, but these errors were encountered:
What would you like?
Currently, within my project, to install packages, I must include the
--force
flag to ensure NPM installs despite some of my dependencies having version compatibility issues. By adding a new key within the cypress step calledinstall_flags
, you could allow users to enter any flags to go along with the npm install.Example:
Why is this needed?
This is useful for my project and potentially many others because some larger projects may contain version dependency errors, and in our case, our app works perfectly fine despite those conflics.
We plan to include Cypress testing within Github actions, but every time the test starts, it fails simply because it fails to install all the required NPM packages within the project.
Image of error occurring in Github actions:
Other
No response
The text was updated successfully, but these errors were encountered: