Permalink
Browse files

No reason to exclude node 0.4.

  • Loading branch information...
1 parent b60fc60 commit 9c043a1eb7fef87ffe3889e7451d2b8925308d2f @ljharb ljharb committed Jan 26, 2014
Showing with 2 additions and 1 deletion.
  1. +1 −0 .travis.yml
  2. +1 −1 package.json
View
@@ -4,6 +4,7 @@ node_js:
- "0.10"
- "0.8"
- "0.6"
+ - "0.4"
@Raynos
Raynos Feb 1, 2014 Contributor

wut. Node 0.4 & 0.6 are dead & unmaintained. They should stay dead

@ljharb
ljharb Feb 1, 2014 Member

Providing an upgrade path, even from old unmaintained versions (node, browser, or otherwise) is part of a module maintainer's responsibility imo. Of course nobody should be using anything but the latest node stable - but there are still production systems using old versions of node, and it harms nothing to ensure tests still pass in them.

before_install:
- '[ "${TRAVIS_NODE_VERSION}" != "0.6" ] || npm conf set strict-ssl false'
View
@@ -37,7 +37,7 @@
"uglify-js": "~2.4.12"
},
"engines": {
- "node": ">=0.6.0"
+ "node": ">=0.4.0"
},
"testling": {
"browsers": [

0 comments on commit 9c043a1

Please sign in to comment.