mirror/nixpkgs - Nix packages collection

Age	Commit message (Collapse)	Author	Files	Lines
2013-01-13	node/bson: fix sha256	Mathijs Kwik	1	-1/+1

2013-01-10	Added optparse: A node.js option parsing library	Sander van der Burg	1	-0/+13

2012-11-23	Add jsontool 5.1.1 (node.js package)	Rob Vermaas	1	-0/+13

2012-11-09	Added swig Node.js package	Sander van der Burg	1	-0/+13

2012-10-31	node-packages: upgrade coffee-script to 1.4.0	Mathijs Kwik	1	-2/+13
	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-27	node-packages: add "escape-html"	Mathijs Kwik	1	-0/+13

2012-10-19	nodePackages.buffertools	Shea Levy	1	-0/+13

2012-10-18	node-packages	Mathijs Kwik	1	-15/+40
	- 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-04	node-packages: upgrade mongodb and bson	Mathijs Kwik	1	-9/+9

2012-10-04	node-packages: add "source-map" and dependencies	Mathijs Kwik	1	-0/+28

2012-09-22	nodePackages.knox	Shea Levy	1	-0/+13

2012-09-22	nodePackages.node-expat	Shea Levy	1	-7/+23

2012-09-20	Add optimist nodePackage	Shea Levy	1	-0/+26

2012-09-19	Add temp nodePackage	Shea Levy	1	-0/+13

2012-09-18	Add cipher-block-size node package and remove the nativeDeps argument to ↵	Shea Levy	1	-1/+31
	build-node-package (buildInputs can just be specified directly)
2012-09-17	node-packages: add 4 packages	Mathijs Kwik	1	-1/+59
	- faye-websocket - node-uuid - rbytes - sockjs
2012-09-17	node-packages: upgrade mongodb and bson (and build native module)	Mathijs Kwik	1	-9/+10

2012-09-17	node-packages: ability to build npms that have native extensions	Mathijs Kwik	1	-2/+3

2012-09-05	npm2nix: Bump to 0.1.3	Shea Levy	1	-5/+5

2012-09-04	node-packages: add a lot of packages	Mathijs Kwik	1	-42/+616

2012-09-04	node-packages: ability to fix sources that use the impure "latest" dependency	Mathijs Kwik	1	-0/+8

2012-09-04	node-packages: introduced alphabet	Mathijs Kwik	1	-169/+169

2012-08-26	Add node-gyp	Shea Levy	1	-0/+311

2012-08-26	Add npm2nix 0.1.2	Shea Levy	1	-8/+8

2012-08-26	Add npm2nix as a nodePackage	Shea Levy	1	-0/+14

2012-08-26	Add semver node package	Shea Levy	1	-0/+13

2012-08-22	node-packages.nix: Export buildNodePackage	Shea Levy	1	-5/+5

2012-07-25	Remove the 'with pkgs;' from node-packages.nix.	Shea Levy	1	-3/+1
	Packages depending on non-node packages should refer to their deps with pkgs.name
2012-07-25	Add coffee-script node package	Shea Levy	1	-0/+12

2012-07-25	Add empty node-packages.nix using build-node-package.nix from npm2nix.	Shea Levy	1	-0/+12
	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