nixpkgs/pkgs/top-level/node-packages.json

[
  "async"
, "assert"
, "mocha"
, "jayschema"
, "underscore"
, "extend"
, "express"
, "s3http"
, "aws-sdk"
, "nijs"
, "amdefine"
, "smartdc"
, "optparse"
, "jsontool"
, "swig"
, "coffee-script"
, "escape-html"
, "buffertools"
, "wu"
, "source-map"
, "knox"
, "node-expat"
, "optimist"
, "temp"
, "faye-websocket"
, "node-uuid"
, "rbytes"
, "sockjs"
, "backbone"
, "browserchannel"
, "node-gyp"
, "semver"
, "npm2nix"
, "ansi-remover"
, "mkdirp"
, "jshint"
]
node-packages.nix: Convert to new npm2nix style Starting with 1.0.0 (which is not released at the time of this commit but will be before it is pushed), npm2nix takes a JSON file with a list of names (and optionally version ranges) and generates a data-only (no functions, no rec, no let, etc.) nix expression representing the packages with those names and their dependencies. node-packages.nix now builds its package list from that generated expression. If a package needs native dependencies as build inputs, they can be added to the nativeDeps attribute set. If a package cannot be generated by npm2nix for some reason, it can be added manually to the set. I tried to capture the packages represented by the previous node-packages.nix in the new node-packages.json, but I almost certainly missed some that will have to be added manually. Signed-off-by: Shea Levy <shea@shealevy.com> 2013-05-28 02:29:00 +00:00			`[`
npm2nix now supports simple strings in the JSON file if no range is specified Signed-off-by: Shea Levy <shea@shealevy.com> 2013-05-28 17:19:44 +00:00			`"async"`
			`, "assert"`
			`, "mocha"`
			`, "jayschema"`
			`, "underscore"`
			`, "extend"`
			`, "express"`
			`, "s3http"`
			`, "aws-sdk"`
			`, "nijs"`
			`, "amdefine"`
			`, "smartdc"`
			`, "optparse"`
			`, "jsontool"`
			`, "swig"`
			`, "coffee-script"`
			`, "escape-html"`
			`, "buffertools"`
			`, "wu"`
			`, "source-map"`
			`, "knox"`
			`, "node-expat"`
			`, "optimist"`
			`, "temp"`
			`, "faye-websocket"`
			`, "node-uuid"`
			`, "rbytes"`
			`, "sockjs"`
			`, "backbone"`
			`, "browserchannel"`
			`, "node-gyp"`
			`, "semver"`
			`, "npm2nix"`
			`, "ansi-remover"`
Add mkdirp as a top-level nodePackage Signed-off-by: Shea Levy <shea@shealevy.com> 2013-05-30 13:05:55 +00:00			`, "mkdirp"`
add nodePackages.jshint 2013-05-30 14:01:18 +00:00			`, "jshint"`
node-packages.nix: Convert to new npm2nix style Starting with 1.0.0 (which is not released at the time of this commit but will be before it is pushed), npm2nix takes a JSON file with a list of names (and optionally version ranges) and generates a data-only (no functions, no rec, no let, etc.) nix expression representing the packages with those names and their dependencies. node-packages.nix now builds its package list from that generated expression. If a package needs native dependencies as build inputs, they can be added to the nativeDeps attribute set. If a package cannot be generated by npm2nix for some reason, it can be added manually to the set. I tried to capture the packages represented by the previous node-packages.nix in the new node-packages.json, but I almost certainly missed some that will have to be added manually. Signed-off-by: Shea Levy <shea@shealevy.com> 2013-05-28 02:29:00 +00:00			`]`