-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Use npm ci instead of install #617
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
Conversation
LGTM, but I know nothing about npm. If no one thinks this will break in some cases, I'll merge! |
I'm not sure that this is a good change - I think This means we reinstall node_modules on every |
0771d32
to
238ebfd
Compare
@DJMcNab Ok, how about this? |
So, npm either ignores lockfile, or purges node_modules completely? 🤦♂️ |
FWIW, I'd personally will be more confident with |
Uh, but I think we might use |
238ebfd
to
0dc60e1
Compare
In a development cycle, I frequently run |
I forgot we had that set up. However, I still want to use rust analyzer when developing it, so I still want the release version of |
For that, I personally do |
618: Add install-lsp subcommand r=matklad a=h-michael related #617 (comment) Co-authored-by: Hirokazu Hata <h.hata.ai.t@gmail.com>
Fair enough - cargo install-code as a blessed subcommand made me not even consider that as an option 🤦♂️. |
Aren't we supposed to use |
that’s what install-code uses, yeah bors r+ |
617: Use npm ci instead of install r=matklad a=h-michael fix #422 `npm install` is always recreate `package-lock.json`. So we might use `npm ci` with `install-code` https://docs.npmjs.com/cli/ci.html#description 618: Add install-lsp subcommand r=matklad a=h-michael related #617 (comment) Co-authored-by: Hirokazu Hata <h.hata.ai.t@gmail.com>
Build succeeded |
fix #422
npm install
is always recreatepackage-lock.json
.So we might use
npm ci
withinstall-code
https://docs.npmjs.com/cli/ci.html#description