3
0
Fork 0
forked from mirrors/nixpkgs
Commit graph

30 commits

Author SHA1 Message Date
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
Shea Levy 7d5bb08534 Add cipher-block-size node package and remove the nativeDeps argument to build-node-package (buildInputs can just be specified directly) 2012-09-18 12:08:16 -04:00
Mathijs Kwik 177a0d761a node-packages: add 4 packages
- faye-websocket
- node-uuid
- rbytes
- sockjs
2012-09-17 09:56:49 +02:00
Mathijs Kwik e0d35483aa node-packages: upgrade mongodb and bson (and build native module) 2012-09-17 09:56:49 +02:00
Mathijs Kwik baa6223904 node-packages: ability to build npms that have native extensions 2012-09-17 09:56:49 +02:00
Shea Levy 7fbf92d8f9 npm2nix: Bump to 0.1.3 2012-09-05 12:22:03 -04:00
Mathijs Kwik b78b5b3f36 node-packages: add a lot of packages 2012-09-04 17:49:32 +02:00
Mathijs Kwik 278312a38c node-packages: ability to fix sources that use the impure "latest" dependency 2012-09-04 17:49:32 +02:00
Mathijs Kwik df82c94263 node-packages: introduced alphabet 2012-09-04 17:49:32 +02:00
Shea Levy 7e24bde3d9 Add node-gyp 2012-08-26 16:18:03 -04:00
Shea Levy ddb3f8c34e Add npm2nix 0.1.2 2012-08-26 16:11:29 -04:00
Shea Levy a94e8d2756 Add npm2nix as a nodePackage 2012-08-26 16:02:04 -04:00
Shea Levy 9a8b0b644b Add semver node package 2012-08-26 15:43:02 -04:00
Shea Levy aa4ce18077 node-packages.nix: Export buildNodePackage 2012-08-22 09:44:38 -04:00
Shea Levy 42da3759a2 Remove the 'with pkgs;' from node-packages.nix.
Packages depending on non-node packages should refer to their deps with pkgs.name
2012-07-25 17:53:02 -04:00
Shea Levy e2576899c1 Add coffee-script node package 2012-07-25 17:51:19 -04:00
Shea Levy c516517656 Add empty node-packages.nix using build-node-package.nix from npm2nix.
buildNodePackage is a function to build npm packages.

npm2nix (https://bitbucket.org/shlevy/npm2nix) can be used to generate subexpressions to go in node-packages.nix
2012-07-25 17:46:21 -04:00