Skip to content

WIP: Support npm workspaces #382

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

Closed
wants to merge 3 commits into from

Conversation

penx
Copy link

@penx penx commented May 31, 2021

Fixes #377

First commit is failing test:

https://github.com/penx/github-action/runs/2709565787?check_suite_focus=true

Second commit is a proposed fix but currently errors with:

The `npm ci` command can only install with an existing package-lock.json

This seems to be because it's trying to run npm ci from within a workspace subfolder, and unlike the yarn equivalent, npm doesn't like that.

@penx penx force-pushed the feature/npm-workspaces branch 4 times, most recently from 8e5678a to 4c488bc Compare May 31, 2021 10:16
@penx penx mentioned this pull request May 31, 2021
@penx penx mentioned this pull request Jun 11, 2021
@penx penx force-pushed the feature/npm-workspaces branch from 4c488bc to a5c20af Compare September 13, 2021 16:20
@penx
Copy link
Author

penx commented Sep 13, 2021

I think in the case of npm workspaces, the best option may be for users to manage the npm install themselves via their github action, and then to pass install: false to cypress-io/github-action as suggested at #145 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error finding package-lock.json within npm workspace
1 participant