aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIgor Pashev <pashev.igor@gmail.com>2019-10-02 11:08:43 +0200
committerIgor Pashev <pashev.igor@gmail.com>2019-10-02 11:08:43 +0200
commit61a691e9f4eb2d428be9095ef5fc2b5a69bff41e (patch)
tree55c72e4e37032ac98be7bd5976add16bf1c16e16
parent0215671c6aab24e1885074761f44c502f0bb00e2 (diff)
downloadnpm.nix-61a691e9f4eb2d428be9095ef5fc2b5a69bff41e.tar.gz
Mention npm4nix
-rw-r--r--README.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/README.md b/README.md
index d49980c..0aa2f10 100644
--- a/README.md
+++ b/README.md
@@ -20,11 +20,13 @@ Guideline](https://www.debian.org/doc/debian-policy/). We build every
JavaScript package from its source code, we can apply any patches, we can
control what is installed.
+To help adding and updaing packages there is the
+[npm4nix](https://github.com/ip1981/npm4nix) utility.
+
To be (maybe) done
==================
-* A tool similar to [cabal2nix](https://github.com/NixOS/cabal2nix).
* Something like `nodeWithPackages`.
* Bundles. For example, a closed set of tarballs, so that NPM can install
them and resolve depenednecies offline. Or simply a bundle with `node_modules`