Closed maxbeizer closed 9 years ago
npm@3 is fundamentally changing how the peerDependencies
attribute functions. My understanding is that yo
should remain as a peer dependency, but the responsibility of managing that dependency has shifted to the consumer of the package (i.e. – you).
From what I understand, this change is an attempt to reduce the likelihood of what npm describes as "dependency hell," where different packages require conflicting versions of a dependency.
We could move yo
to a explicitly dependency, but I'm not sure it's necessary. If someone has information/opinion that states otherwise, I'm definitely open to hearing it.
@dcalhoun :cool: . Just thought I'd mention it as I spun up a new PB site yesterday for the first time in a while. :beers:
or without the warning output:
@dcalhoun should we add
yo
as an explicit dependency? GP version 2.0.1