[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NPM importer

From: Julien Lepiller
Subject: Re: NPM importer
Date: Tue, 20 Nov 2018 08:50:15 +0100
User-agent: K-9 Mail for Android

Well, minimist is not a small package. I have a small script somewhere that 
browse the registry to find recursively the list of dependencies of a package. 
I tried to run it on minimist and I stopped it after a few thousand different 
packages were found. That's also why we can't make a recursive importer: it 
would almost never end.

I think my plan was to build these packages without testing them at all, 
focusing on packaging test frameworks that will be needed to test other 

See this script that builds a graph of dependencies, ignoring devDependencies 
(so none of the packages listed by this script is going to be tested):

Not testing these packages is maybe less problematic than not testing other 
kinds of packages because we are packaging the same thing as developpers test, 
in a similar environment.

I'll push what I have to a wip-branch latter today. The reason why I develop 
out-of-tree is because I can always rebase my patches.

Le 20 novembre 2018 00:29:02 GMT+01:00, swedebugia <address@hidden> a écrit :
>On 2018-11-11 16:37, Julien Lepiller wrote:
>> I improved a bit over jlicht's work here, but there still a few
>tgings we want co work on:
>> There is an importer and a build system as well as a few packages.
>One of tge issue is that the importer is not recursive, so it doesn't
>get the specified version, and the packages aren't tested because the
>tests depend on cylic dependencies (and sometimes very big circles).
>Is there a reason to have this out-of-tree?
>Could you push it to a wip-npm branch in guix?
>Some npm packages has no or almost no dependencies.
>These we could start with if the build-system works and incrementally 
>improve the build-system and the complexity of added packages.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]