-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Run npm install as part of install.py #24568
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this mean we can omit from build.py? it looks like that one is using 'npm ci'... so what is this part for?
Exactly yes. |
What's the difference between 'npm install' and 'npm ci' then? |
npm ci always uses the exact pinned versions I believe... its designed to be reproducible. |
So I guess switching from that to this would be a functional change then. If that's fine, then this PR LGTM. I guess it should be fine to just let it run twice for the few versions after this rolls into emscripten-releases and before we remove the one there? |
The emscripten-releases build script is already using |
ping.. |
Maybe I'm misunderstanding what the intention is then. If we put this into install.py and then remove |
Can you explain why you think its a functional change? We only need to run
My intention is to remove the one from build.py yes. |
oh... uh, nevermind I misread the code, I was thinking we ran literally 'npm install' but it says 'npm ci' ... oops :) |
Ooops, sorry I had auto-commit on. |
No description provided.