chore: downgrade npm to v6 and regenerate package-lock #3013
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
npm v7 causes a multitude of problems, namely that we can't run
npm ci
for the release script since it uses ssh protocol for all dependencies to read from it, which fails if you don't have ssh permissions.I had to downgrade to npm v6 and then delete
package-lock.json
and regenerate it to solve the issue.See npm/cli#2610
See npm/cli#3284
This pr replaces #2996 and includes updated dependencies as well since i regenerated the package-lock file. I hate that we have to downgrade chromedriver from
@latest
to v90 as well, but CircleCI hasn't updated it's version of chrome to v91 and we really need this merged to do the release.