Possible to use new "npm ci" during release?

[bryantrobbins]

Hello,

Is is possible to use the relatively new npm ci command during the release process instead of the default "npm install"? We're attempting to do an automated release against locked package versions.

Would a "--use-ci" flag or similar make sense as a convenient way to enable this? If so, I can look into a PR for the same.

yaodingyd earned $40.00 by resolving this issue!

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on Issuehunt to raise funds.

[sindresorhus]

From the docs:

The project must have an existing package-lock.json or npm-shrinkwrap.json.

So we can just automatically use npm ci when a package-lock or npm-shrinkwrap is present. No flag needed. It removes node_modules too, so we can remove that step when using npm.

We also need to ensure the user is using a recent npm version. I think we should just change this task to require npm v6. No reason not to use the latest npm version.

PR welcome :)

[IssueHuntBot]

@issuehuntfest has funded $40.00 to this issue. See it on IssueHunt

[IssueHuntBot]

@yaodingyd has submitted a pull request. See it on IssueHunt

[IssueHuntBot]

@sindresorhus has rewarded $36.00 to @yaodingyd. See it on IssueHunt

• 💰 Total deposit: $40.00
• 🎉 Repository reward(0%): $0.00
• 🔧 Service fee(10%): $4.00