Github actions - npm install flags

[Multinite]

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 called install_flags, you could allow users to enter any flags to go along with the npm install.

Example:

      - name: Cypress run
        uses: cypress-io/github-action@v6
        with:
          build: npm run build
          start: npm start
          install_flags: 
             - "--force"
          browser: chrome

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

[Jennifer Shehane]

Moving issue to github-actions repo.

[Mike McCready]

@Multinite

Your request for the ability to use an alternate command to install npm dependencies is already available.

Please see the Custom install command parameter install-command, where you could write for instance:

- uses: cypress-io/github-action@v6
  with:
    install-command: npm ci --legacy-peer-deps

[Mike McCready]

I suggest to close this request.