Update nan to 1.8.0 to fix iojs 2.0.0 build

[topaxi]

There are some deprecation warnings in the build though...

Fixes #298

[nmccready]

bump

[MateusZitelli]

👍

[dhritzkiv]

👍 as well.

Suggestion: add iojs targets under node_js to the .travis.yml file:

node_js:
  - "0.8"
  - "0.10"
  - "0.12"
  - "iojs-v1.8.0"
  - "iojs-v2.0.0" 

So we can verify that it compiles and tests properly on iojs

[imyller]

Referencing nodejs/node#1620

[gordalina]

Bump

[cesarandreu]

👍

[kkoopa]

You want 1.8.4, not 1.8.0.

[imyller]

Exactly, 1.8.4 not 1.8.0
My PR #300 for ~1.8 would have bumped to latest 1.8.4 (and then stayed with 1.8.x line), but node.bcrypt.js wants to use exact versions for some reason.

[gordalina]

👍 for 1.8.4

[topaxi]

Updated all dependencies to the newest versions

[alanpurple]

+1

[gordalina]

You could also add in .travis.yml iojs-v1 and iojs-v2

[defunctzombie]

@kkoopa Do you think this is ready to go? no more nan updates that will need to be made immediately?

[kkoopa]

Well, according to current plans, io.js 3.0 with V8 4.3 should come out in a month or so. This will require NAN 2.0, which will have breaking changes to accommodate the Maybe monads introduced in V8 4.3. So you'll have to do some rewriting then, but there is no reason not to do this simple upgrade in the meantime.

On May 6, 2015 9:08:49 PM EEST, Roman Shtylman [email protected] wrote:

@kkoopa Do you think this is ready to go? no more nan updates that will
need to be made immediately?

---

Reply to this email directly or view it on GitHub:
#299 (comment)

[imyller]

Business as usual and an infinite loop :)

V8 evolves. NAN updates accordingly. Packages update NAN dependencies. And then we start all over again.

[nmccready]

Working thank you!