This is one of the most important video in this series and pretty much required to know for every front-end developer. Without knowing these facts if someone upgrade the project and end up in issues then it will be very time consuming and tedious to fix. Mehul thanks for sharing. Keep going good work.
what does lockfileversion do in package-lock.json? One branch in my repository has lockfileversion: 1 and the other branch has lockfileversion: 2 ,what is the meaning of that?
So say we delete node_modules and deleting package-lock.json and reinstalling "npm install" will download the new versions than specified on package.json with possible breaking changes?
Hi Sir I m trying to resolve a scenario, where there is a package called chalk which comes under many parent package, now i f have to upgarde chalk 2.0.0 to chalk 4.2.0 , so that it should also gets update under each parent package as well of the node modules. How can i do that , i m trying to address security vulenarability . Please help Thanks!
How to install dependencies in nodejs project if the project has 2 package.json files. One on root and the other one with dependencies in say libs folder?
so that means after npm install, and if there's newer minor/patch version, npm updates the package but packge-lock.json will not update? But if we explicitly change the version in package.json then it will also update in package-lock.json. correct me if I am wrong
Hi, thank you so much for making this video! It has been very useful! However im stuck on the last part, i have generated the nfts and j.son file on visual studio code however how do i transfer them to a single folder on my laptop please? Please help! Thank you so much - I'll send you an NFT once its out as an appreciation gift! :)
Greate tutorial.!! let say express: ^4.17.1 has the latest version ^4.18.1 after few weeks if i do ( npm install ) in feature, will it install 4.17.1 OR 4.18.1 ?? i need latest version so
This is one of the most important video in this series and pretty much required to know for every front-end developer. Without knowing these facts if someone upgrade the project and end up in issues then it will be very time consuming and tedious to fix. Mehul thanks for sharing. Keep going good work.
crystal clear explanation 🙌🙌
EXCELLENT video. You have such an amazing way of conveying information. Kudos on great content.
I appreciate that!
Amazing explanation, thanks a lot for all the effort recording those videos
2:00 that's minor version, not patch
Minor versions are mainly for security bugs
thank you brother , you are the best teacher.
Excellent video. One thing you did not mention: If I run npm install and I have both files package.json and package-lock.json which one will be used?
that's amazing video, thank you so much!
what does lockfileversion do in package-lock.json? One branch in my repository has lockfileversion: 1 and the other branch has lockfileversion: 2 ,what is the meaning of that?
lockfileversion 2 was inttroduced in npm 7 and this guy is using npm 6
So say we delete node_modules and deleting package-lock.json and reinstalling "npm install" will download the new versions than specified on package.json with possible breaking changes?
wow.. thanks for the this series.
Clear and good explanation! Thanks!
Hi Sir
I m trying to resolve a scenario, where there is a package called chalk which comes under many parent package, now i f have to upgarde chalk 2.0.0 to chalk 4.2.0 , so that it should also gets update under each parent package as well of the node modules.
How can i do that , i m trying to address security vulenarability .
Please help
Thanks!
Beautifully explained!
So why even use the "~" & "^" in your package.json?
If I don't use them then I will never have these conflicts, isn't it so?
Definitely. But one of your dependencies also could use those "~" & "^" version for their own dependencies and that is the issue.
How to install dependencies in nodejs project if the project has 2 package.json files. One on root and the other one with dependencies in say libs folder?
so that means after npm install, and if there's newer minor/patch version, npm updates the package but packge-lock.json will not update? But if we explicitly change the version in package.json then it will also update in package-lock.json. correct me if I am wrong
I am getting this: 20 vulnerabilities (3 moderate, 16 high, 1 critical). How to resolve this. But i think issue is in package-lock.json file
but how do we use it to install packages? clearly npm install won't work, right?
Excellent
Thanks Muhammad! :)
And do not forget to commit this package-lock.json file.
Learn package.lock.json in Hindi - th-cam.com/video/fsAHuwF53KU/w-d-xo.html
Hi, thank you so much for making this video! It has been very useful! However im stuck on the last part, i have generated the nfts and j.son file on visual studio code however how do i transfer them to a single folder on my laptop please? Please help! Thank you so much - I'll send you an NFT once its out as an appreciation gift! :)
hi mehul..i am searching for the playlist of this video? please update it in description..
th-cam.com/play/PLYxzS__5yYQmf-iF_9MTZmx7TxnmwnKIk.html
actually doesn't explain how -lock file is working. NPM takes lock file in consideration only with ci install
can you share your PS1 variable? Thanks
Greate tutorial.!!
let say express: ^4.17.1 has the latest version ^4.18.1 after few weeks
if i do ( npm install ) in feature, will it install 4.17.1 OR 4.18.1 ??
i need latest version so