Skip to content

Save lockfile state after running npm install #2726

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

Merged
merged 1 commit into from
Aug 29, 2020

Conversation

jtgeibel
Copy link
Member

I think this is the first time I've run npm install locally since the switch to Renovate, but I'm not certain where this drift came from.

r? @Turbo87

@Turbo87
Copy link
Member

Turbo87 commented Aug 29, 2020

hmm... interesting. what npm version are you running locally? maybe that could be causing the diff 🤔

@jtgeibel
Copy link
Member Author

I've been running node 14.x since April, but this is the first I've ended up with local changes. I'm currently on node v14.9.0 and npm 6.14.8. (The latest LTS release, node 12.8.3, appears to come with npm 6.14.6, so no much difference there.)

@Turbo87
Copy link
Member

Turbo87 commented Aug 29, 2020

strange. OTOH I've found several issues where people were complaining about similar issues (dev flags changing between npm install runs). never had any such issues with yarn so far. I'll see if npm has something similar to yarn install --frozen-lockfile.

I'll merge this for now and keep monitoring it.

@bors r+

@bors
Copy link
Contributor

bors commented Aug 29, 2020

📌 Commit 393c31b has been approved by Turbo87

@bors
Copy link
Contributor

bors commented Aug 29, 2020

⌛ Testing commit 393c31b with merge 6379489...

@bors
Copy link
Contributor

bors commented Aug 29, 2020

☀️ Test successful - checks-travis
Approved by: Turbo87
Pushing 6379489 to master...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants