[Top][All Lists]

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

Re: NPM importer

From: swedebugia
Subject: Re: NPM importer
Date: Fri, 23 Nov 2018 20:50:36 +0100

On 2018-11-22 02:02, swedebugia wrote:

On 2018-11-22 00:22, swedebugia wrote:

A graph of all npm packages and top packages is also available:

This graph is in-degree and does not consider versions. It is useful only to see the relative popularity of libraries. It does not reveal the out-degree which is what we are interested in: recursive dependencies (given x what does it take to build x? build and test x?) Also it leaves out any information about licensing. It would be nice with a graph of which npm packages has which licenses with licenses as vertices/nodes and packages as edges.


See also the issue I created here:

And similar here:
Got an answer which is good news for building and bad news for testing:

  "devDependencies": {
"coveralls": "^2.11.2", // NOT NEEDED: Posts coverage reports to
    "docco": "*", // NOT NEEDED: Builds docs
"eslint": "1.10.x", // Needed for linting (not sure if you think of linting as part of testing)
    "gzip-size-cli": "^1.0.0", // NOT NEEDED
    "karma": "^0.13.13", // Needed for testing
    "karma-qunit": "~2.0.1", // Needed for testing
    "karma-sauce-launcher": "^1.2.0", // Needed for testing
    "nyc": "^2.1.3", // Needed for testing
    "pretty-bytes-cli": "^1.0.0", // NOT NEEDED
    "qunit-cli": "~0.2.0", // Needed for testing
    "qunit": "^2.6.0", // Needed for testing
    "uglify-js": "3.3.21" // Needing for building

In summary direct devdeps: 1 needed for building, 6 needed for testing.

uglify-js is a minifier used in a lot of projects and the only one needed for this specific project.

For packages like this we could probably patch the package to skip the minifying step and let the user choose which minifier (if any) to use.

In this particular case the minifier compacts the code from 57KB -> 17.6KB.

The most important thing I think is to be able to start packaging this mess so cutting an arm and a leg in the beginning (= skip minification and testing is warranted in my view).

In this case the only thing left to do to package underscore is to:
1) name it: e.g. node-underscore (like debian)
2) decide whether to delete the minified upstream or not in the guix package.



reply via email to

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