Why are there so many cyclic dependencies?

[Daniel-Khodabakhsh]

What's going on? Is there something I'm missing?? Why would it be setup this way?

Here are two examples from a non-exhaustive search:

node-d@1.0.2 -> node-es6-iterator@2.0.3 -> node-es5-ext@0.10.64 -> node-d@1.0.2
node-es6-iterator@2.0.3 -> node-es5-ext@0.10.64 -> node-es6-iterator@2.0.3

[medikoo]

@Daniel-Khodabakhsh what you see is simply a circular dependency, which is intentional between those packages

[Daniel-Khodabakhsh]

@medikoo Why would it be setup this way?

[medikoo]

@medikoo Why would it be setup this way?

@Daniel-Khodabakhsh follow on how those dependencies are used and in what context, and you should get the answer

e.g. es5-ext provides shim of utils that expose ES2015 iteretors (hence dependency on es6-iterator. While es6-iterator depends on some other basic utils from es5-ext (hence the dependency on es5-ext)

Also note that es5-ext provides just extensions to interfaces, and not whole interfaces (those are exposed with individual packages)