peer dependencies can be changed to plain dependencies as of npm3

[webpack-contrib]

peer dependencies can be changed to plain dependencies as of npm3

[nkbt]

Peer deps are not deprecated and libraries are encouraged to use them to give devs more freedom. So devs can potentially use incompatible versions that can still work well.

Dependencies work in a different way and do not suit for writing small libs/plugins.

[MoOx]

Agree with @nkbt.

[Pomax]

Wait, no they don't? As far as the docs surrounding NPM3 suggest, peer dependencies and plain dependencies now work exactly the same. Version conflicts are simply resolved by giving the module that needs a conflicting version w.r.t. the version already found at the root level its own local ./node_modules dir, which solves the conflict due to how dependency resolution still happens (bottom-up, checking local, then up until the project root, then system cache). They're not "deprecated" in the sense that they'll still work, but the need for them has vanished as of npm3.

[nkbt]

@Pomax this is not how dependencies and peerDependencies work. Peer dependencies do not resolve themselves for a library if version is incompatible with end-product. Dependencies do. Which means you end up with, for example, two React libraries in your project if you use dependencies instead of peer ones. With peer deps you as a developer will decide if you are ok with using incompatible peer dep (that is used in your product), and that might work out well.

[Pomax]

I see, thanks.

[nkbt]

np 👌