Npm Package Lock vs Yarn Lock - You Need Lock Files

[@MonsterlessonsAcademy]

Watch next: How to Remove Already Tracked File in Git - kzbin.info/www/bejne/gIvalIGKls6ihaM

[@danyalsaleem5883]

This is the first time in my five years of development, understood that concept. Great video.

[@MonsterlessonsAcademy]

Great to hear!

[@ks6115]

Very good video about concepts and most important with examples! Well explained, thks!

[@MonsterlessonsAcademy]

Glad it was helpful!

[@hughluo8494]

Great explanation, thanks 💯

[@MonsterlessonsAcademy]

Glad it was helpful!

[@ytbcmt4686]

Respect from India

[@MonsterlessonsAcademy]

Thank you!

[@ertugrulgurler9901]

Thank you !!

[@MonsterlessonsAcademy]

You're welcome!

[@TAO7TAO7]

Thanks

[@MonsterlessonsAcademy]

Welcome!

[@StreetGuy911]

привіт! є питання: якщо уявити ситуацію, що наші депенденсі ссилаютсья на ріізні версії одної і тої ж ліби, як це відобразитьсся в лок файлі? і яка версія в результаті буде обрана?

[@MonsterlessonsAcademy]

Привет. Если депенденси могут использовать одну версию те >1.0

[@valendis]

Sure I will spend half of my time fixing conflicts in the lockfile, no one working in a company will do this, next you'll tell me to fix conflicts in my built and minimized webpack output file 😅 I get the point but nowadays it's not possible, I use ncu to update packages and everytime I do this I clear the lockfile. So it's useful for the new dev that just want to npm i but that's pretty much it

[@MonsterlessonsAcademy]

It looks like you are missing the point. If you open any project that exists it will have a lock file. Every time when you "just remove" lock file you app can break because a dependency of dependency was updated. So removing it is not a typical or safe workflow for any company.

[@ytbcmt4686]

Subbed

[@subhranshudas8862]

Take a shot every time he says "dependency"

[@MonsterlessonsAcademy]

This programmers games :D