Shea Levy
03858122be
D'oh
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-11-14 14:15:39 -05:00
Shea Levy
60428f1d49
In nodePackages.patchSource, make the source tree writable
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-11-14 14:11:53 -05:00
Shea Levy
0b0bded848
Better json parsing
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-11-14 13:58:38 -05:00
Shea Levy
5fa298c1aa
Update npm packages to latest npm2nix
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-11-14 13:36:08 -05:00
Shea Levy
9817bada91
Update nodePackages to npm2nix-5.2.0
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-11-05 18:02:21 -05:00
Rok Garbas
9ffc2dff98
updating node packages and adding few to the json list
...
- bower
- grunt-cli
- grunt-contrib-jshint
- grunt-contrib-requirejs
- grunt-contrib-less
- grunt-contrib-cssmin
- grunt-contrib-uglify
- grunt-karma
- karma-mocha
- karma-coverage
- karma-requirejs
- karma-sauce-launcher
- karma-chrome-launcher
- karma-junit-reporter
- almond
- lcov-result-merger
- coveralls
2013-09-04 19:29:15 +02:00
Rob Vermaas
de9a2c342e
Make generated node expression overridable in nodePackages.
2013-08-26 21:55:48 +02:00
Shea Levy
7188cc39fa
Add karma nodePackage
...
Required updating to npm2nix 5.1.0 for peerDependency cycle management
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-08-20 18:56:20 -04:00
Shea Levy
33575ab335
Update nodePackages to latest npm2nix
...
This version has a much cleaner interface, should require fewer major version bumps
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-08-20 13:12:56 -04:00
Shea Levy
a6887c5973
Update nodePackages to npm2nix 4.0.0
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-08-20 11:52:28 -04:00
Shea Levy
67eb2c8ad3
Handle peerDependencies in nodePackages
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-08-18 19:28:51 -04:00
Shea Levy
595b8dbab9
Revert "Make all node packages available at the top level via their real name/version"
...
This makes attributes visible to nix-env that can't actually be
specified with -A, which is why there is a separate top-level in the
first place, duh.
This reverts commit ddb8b7f831
.
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-08-16 15:30:49 -04:00
Shea Levy
ddb8b7f831
Make all node packages available at the top level via their real name/version
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-08-15 09:57:07 -04:00
Shea Levy
2762b0667d
node-packages.nix: Actually use nativeDeps
...
Wonder how long that's been broken...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-07-27 13:33:18 -04:00
Shea Levy
a895082e56
nodePackages: Update to npm2nix 2.0 format
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-07-14 14:41:53 -04:00
Shea Levy
9efcf4f6fe
Make nodePackages individually overridable
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-31 13:27:55 -04:00
Shea Levy
210246266d
Make overrides of nodePackages work
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-31 12:50:28 -04:00
Shea Levy
758f20f0b8
node-packages.nix: Move non top-level attrs to a sub-attr `full'
...
Since `full' isn't recursed into for derivations, nix-env -qaP * won't
show attributes with problematic characters.
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-31 12:38:26 -04:00
Shea Levy
8e724713c6
Make the function to import npm2nix-generated packages accessible outside of node-packages.nix
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-29 11:22:23 -04:00
Shea Levy
239d532095
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-27 22:35:20 -04:00
Sander van der Burg
9faa4f4b7b
Added async-0.2.8 nodejs package
2013-05-16 18:18:36 +02:00
Sander van der Burg
259b1f931f
Added assert: Node.JS assert module and its dependencies
2013-05-16 12:18:23 +02:00
Sander van der Burg
098fb6d70d
added mocha: simple, flexible, fun test framework for JavaScript and its dependencies
2013-05-16 11:49:21 +02:00
Sander van der Burg
bfd5124bde
jayschema: JSON schema validator NodeJS package
2013-05-14 11:27:44 +02:00
Shea Levy
a88306b15f
nodePackages.underscore: Update
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-06 12:56:15 -04:00
Shea Levy
c2a2a03210
Add extend nodePackage
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-06 12:47:46 -04:00
Shea Levy
15bdde9071
Add express nodePackage
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-06 09:29:33 -04:00
Shea Levy
48a4e91989
nodePackages.patchLatest: Handle tarballs whose root directories are already named 'package'
...
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-04-03 07:41:02 -04:00
Rob Vermaas
2fe5c12d35
Add s3http node package
2013-04-01 17:45:18 +02:00
Shea Levy
cf019ab91e
Add git prerelease of aws-sdk nodePackage
...
Required modifying patchLatest to handle tarballs that don't create a 'package' directory
Signed-off-by: Shea Levy <shea@shealevy.com>
2013-04-01 10:51:22 -04:00
Rob Vermaas
6796240289
Add aws-sdk and deps (node library)
2013-03-29 15:04:02 +01:00
Sander van der Burg
5add198e3d
nijs: updated to 0.0.5
2013-03-23 15:24:59 +01:00
Sander van der Burg
3d55f1d222
nijs: Bump to 0.0.4
2013-03-11 17:43:59 +01:00
Patrick Lee
4105b593a5
upgrading uglify to 2.2.5, optimist to 0.3.5, upgrading source-map to 0.1.7, and adding amdefine
...
Fixes #337
2013-02-26 09:45:43 -05:00
Sander van der Burg
2fca1deeb2
nijs: Added nodejs package
2013-02-26 11:07:16 +01:00
Shea Levy
7783c274fd
Add smartdc nodePackage (and its many dependencies)
2013-02-24 20:26:28 -05:00
Mathijs Kwik
2738f6d5cc
node/bson: fix sha256
2013-01-13 14:54:26 +01:00
Sander van der Burg
7242b4994e
Added optparse: A node.js option parsing library
2013-01-10 13:39:24 +01:00
Rob Vermaas
410b72e807
Add jsontool 5.1.1 (node.js package)
2012-11-23 14:20:48 +01:00
Sander van der Burg
42238e4934
Added swig Node.js package
2012-11-09 18:02:44 +01:00
Mathijs Kwik
0dd3996ab4
node-packages: upgrade coffee-script to 1.4.0
...
I'm not sure yet how to handle these upgrades.
Should we keep the old version around?
Should we only keep it around if other pkgs in nixpkgs depend on it?
Probably people develop their own projects (that are not in nixpkgs)
on top of these and we don't want to break these.
For now, I think it's best just to keep old versions around, but
update the (unversioned) link to the latest.
External projects should then depend on explicit version numbers if
they don't want stuff to break.
If a certain package has +5 versions in nixpkgs, we can clear out the
unuseful ones.
2012-10-31 08:39:05 +01:00
Mathijs Kwik
11228a3834
node-packages: add "escape-html"
2012-10-27 13:06:53 +02:00
Shea Levy
c93786bc7e
nodePackages.buffertools
2012-10-19 16:21:24 -04:00
Mathijs Kwik
e0e00a86cb
node-packages
...
- add async-0.1.22
- add wu-0.1.8
- upgrade mongodb-1.1.11
- upgrade bson-0.1.5
- upgrade underscore-1.4.2
2012-10-18 15:23:56 +02:00
Mathijs Kwik
55f97f3a0d
node-packages: upgrade mongodb and bson
2012-10-04 10:40:51 +02:00
Mathijs Kwik
2f6a498b52
node-packages: add "source-map" and dependencies
2012-10-04 10:40:51 +02:00
Shea Levy
48395bd3e4
nodePackages.knox
2012-09-22 09:32:37 -04:00
Shea Levy
a45a8698b3
nodePackages.node-expat
2012-09-22 09:29:51 -04:00
Shea Levy
a9f8dd2c13
Add optimist nodePackage
2012-09-20 14:08:40 -04:00
Shea Levy
99571aa242
Add temp nodePackage
2012-09-19 12:45:05 -04:00