Re: NPM importer

[Julien Lepiller]

Thanks! It made me wonder if we could better approximate the set of needed 
dependencies by looking at package tags. I'll try to improve my script in that 
spirit, and share it again here.

I think once we have a clearer view of what we want, we should focus on finding 
the best way forward: what packages do we need first, etc. I think build tools 
are obviously more important than test tools, which should have a greater 
priority than the rest of packages.

Le 22 novembre 2018 02:02:52 GMT+01:00, swedebugia <address@hidden> a écrit :
>Hi
>
>On 2018-11-22 00:22, swedebugia wrote:
>snip
>
>> A graph of all npm packages and top packages is also available: 
>> https://exploring-data.com/info/npm-packages-dependencies/
>
>While investigating the top libraries* packages with most depends in
>npm 
>I found the following:
>
>Lib            Dep     DevDep  RecdevDep       Dependants      license
>underscore     0       12      2400+           18000+          mit
>async          1       37      2696            26069           mit
>
>rec=recursive
>
>See also the issue I created here: 
>https://github.com/caolan/async/issues/1600 asking which of asyncs 37 
>devdeps are needed to build or build+test async.
>
>And similar here: https://github.com/jashkenas/underscore/issues/2790