Closed stephenmathieson closed 4 years ago
@stephenmathieson I think npm ci
falls back to npm i
in cases where there is no package-lock? I would be happy to switch between npm and yarn based on the existence of a yarn.lock
(once I get this action working).
Unfortunately it does not:
$ npm ci
npm WARN prepare removing existing node_modules/ before installation
npm ERR! cipm can only install packages with an existing package-lock.json or npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or later to generate it, then try again.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/stephen/.npm/_logs/2020-01-23T16_08_47_954Z-debug.log
Alright, I've added support for checking package-lock.json
and yarn.lock
in 95122d396b7923377f6fca032b38b648aa45fbe2, released as a patch to v1.
Thanks!
It would be nice to support installing deps with Yarn rather than npm. Alternatively just doing
npm install
rather thannpm ci
for projects withoutpackage-lock.json
files would work