-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add option to run a different install command #7
Comments
thdk
added a commit
to thdk/install-changed
that referenced
this issue
May 18, 2020
'hashFileName' and 'command' can now be specified for both cli and api version. users may now specify --command="npm ci" if they would prefere that over "npm install" they can also change the filename of the file that contains the hash with --hashFileName api function watchFile now has a options argument: { hashFileName: string | undefined, command: string | function } Fixes ninesalt#7
Merged
@ryanburnette @the21st |
@thdk that looks great, thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, thanks again for creating install-changed! It's helped me a lot in everyday productivity.
The only issue I'm having with my new flow is that sometimes the
npm install
command that this runs changespackage-lock.json
and I end up with unexpected changed file in my repo.For this purpose, there's
npm ci
which installs from the lockfile, is potentially faster, and doesn't change package-lock.json. Could you add an option to enable runningnpm ci
instead ofnpm install
if thepackage.json
file is changed?The text was updated successfully, but these errors were encountered: