How npm resolves dependency hell | Must know!

[@harshadevapriyankarabandar5456]

Greatest explanation on the KZbin about dependencies. thank you

[@MayankSrivastava]

You're very welcome!

[@jasonvictor1798]

Wow - this was a great video! super helpful.

[@elco7956]

Also try the npm ls command

[@MayankSrivastava]

will give a try

[@stefanhupp7945]

Really nice explanation. Thanks for the information

[@MayankSrivastava]

Glad it was helpful!

[@kshitizbathwal4236]

This was a very helpful and well explained video! Thanks. Looking for more..

[@MayankSrivastava]

More to come!

[@mahalingamsundararaj7003]

Clear explanation

[@OscarRosner]

amazing video.

[@mattalizadeh3918]

That's all good, but the question is if this is already implemented, why do we still get dependency conflicts in the latest versions??

[@ryanwoods3333]

thank you!!

[@d3.finance]

Super helpful. Thank you!

[@MayankSrivastava]

Glad it was helpful!

[@shan504]

Fantastic explanation!

[@MayankSrivastava]

Glad you liked it

[@joelmatthias]

For completeness, it would be good to explain what happens when the major versions are the same, but the minor versions differ. Does npm just install the most recent version of the two versions?

[@MayankSrivastava]

depends on whether you add ^ or ~ in front of the package name

[@nifesalilislam1189]

I have difficult time finding the changelog of some packages, is there a way to do that easily

[@dannyisrael]

Thank you! 🙏🏻

[@coolsai]

nice!!!

[@atharvparlikar8765]

great explenation but it could have been a 2 minute video. great for beginners tho

[@MayankSrivastava]

Thanks for the tip

[@Userkazt]

this mean npm cause duplication of dependency. right ?

[@MayankSrivastava]

Yes, in the case of installing two major versions of the same package

[@KartikVasudev-xz5gp]

Are there any changes to this pattern after npm version 3

[@MayankSrivastava]

not really, it has been resolving conflicts the same way since