What is NPM's package-lock.json?

[@FengolZA]

For years I've had the lock file my project and finally bit to bullet to try and understand what it is. This video couldn't make it any clearer. Thank you so much!

[@JamesQQuick]

Great explanation. Love the overall video as well. Fun stuff!

[@krishnakandula6587]

The presentation and the conceptual clarity of the video is unbelievable. Thank you.

[@VidyaHarnal-r9y]

Great video, you explained it so accurately. Cleared a lot of blur about the package-lock json file. You should make more videos.

[@reidmoffat7055]

This way you presented this video is incredible; incredibly informative & clear and straight to the point - in 3 mins you answered all my questions better than all the stack overflow questions I've read over the last few years. Incredible channel 🙏

[@iurysza]

You're very good at this! Quality content, great editing, great humor.

[@akashkeshari5699]

Hi @Tom, I am using yarn in my project and got yarn.lock file. Still the project does not build up when I tried building with "yarn build" command which was actually building earlier.

[@snake1625b]

Great explanation! It seems like the lock also includes the versions of the sub dependencies as well

[@poppin_party]

thanks bud, I finally understand wth package-lock is

[@sundarraj9384]

Simple, Clear and Good

[@Ahmed-fq3kz]

great informative video with some comedic scenes. I think you will fit perfectly as voice over

[@yashpratapsingh1527]

Awesome explanation, thanks!

[@rajatguleria4933]

Awesome bro, I watched some videos on the same and thought of the same question why would ^ be in the package.json and lock.jason file exist together but no one mentioned the same except you.

[@aakashpatel9281]

really appreciate the video . Keep it up 👍

[@aben5960]

I really appreciate your efforts to produce such an amazing video :)

[@randalljosue]

But what about the fact package-lock.json also has ~ and ^? It would just then NOT install the exact version of packages...

[@b25671]

Why didn't npm just change the functionality of "npm install"... which installs and automatically updates ... to just "install"... without the automatic update And if you want to update the packages... you use the "npm update" command ... like you do now? I don't get it.

[@harshasinha5499]

beautiful answers explained nicely

[@RavenFelman]

thank you so much!

[@lightoo4343]

Should we ever delete lock file? How will it affect dependencies ? Amazing content !😊

[@TomGregoryTech]

There's no reason to delete it. You might get different dependency versions to someone else using the same repo.

[@lightoo4343]

@@TomGregoryTech thank you so much 😊

[@prabhsharansingh6150]

Too good!

[@MayankGupta303]

Thank you

[@GregorGramlich]

I know lock files from the various package managers of Ruby, Python and NodeJS. A similar functionality exists for Gradle (Locking dependency versions in the user guide). Why seems to be so little talk about that? Why don't you - as the Gradle guy - talk about it or mention the parallels in this video? Are the other Gradle mechnisms prefered over locking dependencies? I honestly don't understand why this feature seems to be so unpopular for Gradle.

[@valikonen]

Jesus Bob you have a talent to speak outside of topic....I hope your mom will cut your access to internet ;)

[@RichardRebeco]

gracias amigo

[@user-ed1jc6xl9r]

omg thx u

[@Draconicrose]

Oh. OH! Oh wow. Okay. THEN WHY DON'T THEY JUST SAY SO- /sigh. Thank you for the video.

[@pstha4537]

too many useless content. Get to the point. make it concise.

[@Markus-iq4sm]

Weak explanation

[@ShoaibBinAllahBakhsh]

console.log("Excellent explanation");