Target consistent node envs in travis across all repos about fxa HOT 9 CLOSED

Related: #41 (which I should really do something about since my dumb face is on the ticket).

Also, we should look at ignoring Node 4.x failures until we are confident that Node 4 works for our projects. Something like this pseudo code from fxa-auth-db-server:

matrix:
  allow_failures:
    - node_js: 4
  fast_finish: true

from fxa.

node_js:
  - "0.10"
  - "0.12"
  - "4"

I'm happy with that. And @pdehaan's suggestion is good, but if a module just doesn't compile on 4.0, then testing on 2.0 is better than just spinning travis-ci on some dependency known to fail on 4.0 due to not being updated for NAN 2.0.

from fxa.

Backlogged until all of our modules compile on node 4

from fxa.

Saw this over the weekend: https://twitter.com/seldo/status/646463678410174465
Seems to be some decent justification that we shouldn't really care about testing on io.js.

Major(ish) node versions, requests in last 7 days:

VERSION	REQUESTS
0.12	779 MM
0.10	732 MM
4	222 MM
2 (iojs)	22 MM
3 (iojs)	19 MM
1 (iojs)	6 MM

from fxa.

Backlogged until all of our modules compile on node 4

What are the known blockers?

from fxa.

What are the known blockers?

One is updating for @dannycoates' scrypt-hash fix.

from fxa.

IIUC from a chat with Danny in IRC, scrypt-hash should be ready to go as of its latest release.

from fxa.

Which re-reading your comment, is probably what you meant by "@dannycoates' scrypt-hash fix", never mind me...

from fxa.

Pretty much fixed with the node 4 updates

from fxa.