lukechilds/node - node - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Forrest L Norvell	1e2fa1537f	deps: upgrade npm to 2.6.0 PR-URL: https://github.com/iojs/io.js/pull/904 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>	10 years ago
Forrest L Norvell	af1bf49852	deps: upgrade npm to 2.5.1 PR-URL: https://github.com/iojs/io.js/pull/738 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>	10 years ago
Forrest L Norvell	faf34ffbd3	deps: upgrade npm to 2.4.1 PR-URL: https://github.com/iojs/io.js/pull/663 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>	10 years ago
Forrest L Norvell	f5b35dbda4	deps: upgrade npm to 2.3.0 * Windows improvements: no more uid is undefined errors, use `%COMSPEC%` when set in preference to hardcoded `cmd`, improved handling of Git remotes. * Add caching based on Last-Modified / If-Modified-Since headers in addition to Etag-based cache validation. PR-URL: https://github.com/iojs/io.js/pull/573 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>	10 years ago
Forrest L Norvell	e79ccee168	npm: upgrade to v2.1.18 PR-URL: https://github.com/iojs/io.js/pull/266 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>	10 years ago
Timothy J Fontaine	28ae70ebad	npm: Upgrade to v2.1.6	10 years ago
Timothy J Fontaine	9fad8958df	deps: upgrade npm to 2.0.0	10 years ago
Timothy J Fontaine	daca803e9e	npm: Update to 1.4.28	10 years ago
Timothy J Fontaine	1223cafea6	npm: Upgrade to v1.4.21	11 years ago
isaacs	bd547d6598	npm: upgrade to 1.4.6 * Documentation upgrades * Fix glob bug which prevents proper README publishing * node-gyp upgrade to 0.13 * Documentation updates * Add --save-exact to save an exact dep (instead of a range) * alias 't' to 'test'	11 years ago
isaacs	217bb0c964	npm: upgrade to 1.4.3	11 years ago
isaacs	2a741f2d12	npm: upgrade to 1.3.21	11 years ago
isaacs	e10c223eb6	npm: upgrade to 1.3.20 The 1.3.19 release had a critical bug: any packages published with it could not be installed, because the shasum would be incorrect. Thankfully, 1.3.19 was published using 1.3.19, so could not be installed by any users! However, if it goes out as part of a Node.js release, then obviously that would be a problem.	11 years ago
isaacs	97738994e0	npm: Upgrade to 1.3.19	11 years ago
isaacs	5abdef790c	npm: Upgrade to 1.3.8	12 years ago
isaacs	5e86519199	npm: Upgrade to 1.3.4	12 years ago
isaacs	2bcb9ab7bc	npm: Upgrade to 1.1.55	13 years ago
isaacs	9d4362403c	npm: upgrade to 1.1.41	13 years ago

18 Commits (ae7a23351f7e5b06ab88b7ea9c18d7c5b2e287e9)