A package depending on itself is just an accident (and probably something npm ought to detect on publish and reject, but alas...) However, I believe a 1-packag

A package depending on itself is just an accident (and probably something npm ought to detect on publish and reject, but alas...) However, I believe a 1-package circular dependency is often the result of a developer mistakenly adding a package as a dependency when they mean to add it to `peerDepedencies`: e.g. in TFA: "babel-core depends on babel-register, which depends on babel-core... yeoman-generator depends on yeoman-environment which depends on yeoman-generator." Peer dependencies, of course, no longer exist because it got deprecated because raisins. Which leaves us with zero options to define sideways dependencies.