io.js (old node versions) bug !!

[3imed-jaberi]

I used travis ci for my project with this config:

os:
  - windows
  - linux
  - osx
language: node_js
node_js:
  - 0.10
  - 0.12
  - 1.8
  - 2.5
  - 3.3
  - 4.9
  - 5.12
  - 6.17
  - 7.10
  - 8.16
  - 9.11
  - 10.15
  - 11.15
  - 12.3
  - 'lts/*'
  - 'node'
...

All versions succeeded on all platforms except 3 versions on Windows ( 1.8, 2.5 and 3.3 ).
There is a notification that the NODE version isn't in the remote 🤔 !!
check here.

screenshots:

success :

failed:

• 1.8 :

• 2.5:

• 3.3:

[jasongin]

iojs builds come from a different server. So you'll need to add a different nvs remote config for iojs:

nvs remote add iojs https://iojs.org/dist/

Then the versions should be specified with the iojs/ prefix, e.g. iojs/3.3

[ljharb]

Note that nvm.sh (and thus travis-ci) automatically supports iojs-v1-style specifiers that fetch from iojs.org.

[3imed-jaberi]

Thank you guys for the quick answer ❤️ ..
How can I solve this on Travis CI !!

[jasongin]

I don't think there is a way to do it without changes to nvs or Travis CI to better support this scenario. But is it even worth it? How many package maintainers are still supporting such old node versions?

[3imed-jaberi]

I know this, I am working on a package that should be compatible with all versions of Node JS supported by Express JS .. So, I will override these releases because as you know the problem isn't with the package but by using the NVS inside Travis CI.

Thank you again guys.

[ljharb]

I'm supporting down to node 0.6 on over 250 packages, including all iojs majors ¯\_(ツ)_/¯