16 comments

[ 3.3 ms ] story [ 39.6 ms ] thread
This is really neat, I love graphs and maps like this!
Next all you need to add is graphs of the maintainers.
Very interesting idea!

What would be a connection between two maintainers? If their packages depend on each other, or if they co-maintain a package?

This is really neat! I love knowing how much a package depends on when I decide which to go with.
This is great idea! :-)

Am I the only one that looks at some of these graphs and thinks OMG THE BLOAT! and runs in the opposite direction? These days with a lot of app dev the deps go deep and a tool like this draws a very informative picture.

Thank you :)!

I used to be worried by amount of dependencies too, when I was transitioning from .NET stack to js. Until I realized that each module is usually very small, doing only one thing, and most of the time doing it well.

Now I'm thinking of them in terms of code reuse. Code reuse is good

great work as everybody else said! would be awesome to see the sizes of the modules, too
Thank you! The size in bytes or something else?
(comment deleted)
As long as everybody else is putting their wished for feature here, I'd like to have multiple root nodes at the same time.
great work. something like this already exists, but it's intended for amazon searches and supports npm too. http://www.yasiv.com/npm#view/dat

it's also not very googleable and it's poorly advertised, but it's also cool.