search

TkDodo / blog-comments

6 stars 1 forks source link

blog/solving-conflicts-in-package-lock-json #3

Closed utterances-bot closed 2 years ago

utterances-bot commented 4 years ago

Solving conflicts in package-lock.json | TkDodo's blog

Why you should never delete package-lock.json and how npm can solve the conflicts for you

https://www.dorfmeister.cc/blog/solving-conflicts-in-package-lock-json

brahambence commented 3 years ago

Thanks for the tip! It came handy.

chelsea-codes commented 3 years ago

Wish I knew this sooner! Great explanation and solution! Thanks!

AchmadWahyu commented 2 years ago

The explanation was get me into the adventure!, thank you!

femans commented 2 years ago

very useful, thanks

lizkaufman commented 2 years ago

Thanks! This is really helpful.

Pigeo commented 2 years ago

After running npm install --package-lock-only, if it says "no such file or directory in ./node_modules/foo_bar_bla_bla" then you may need to get the recently added modules by running npm install once again (this time without the --package-lock-only). And in case your node_modules directory got messed up during the process, you may need to delete the node_modules directory before running this npm install once again. So it's not just npm install --package-lock-only and voilà... You may still have some extra steps to perform after that.