opened 04:13PM - 12 Sep 15 UTC
closed 08:33PM - 21 Oct 15 UTC
Doesnt look like nan2.x will be a breaking change and still supports all node ve…rsions we support, ie this will not be a major release
#566 is the PR we're working on. It appears to be generated by one of the following migration scripts [ update_to_nan_v2.0.x.sh](https://gist.github.com/thlorenz/7e9d8ad15566c99fd116) [1to2.js](https://github.com/nodejs/nan/blob/4ed41d760313b648b4d212d6ff5374668757be4f/tools/1to2.js)
If youd like to get ahead of us and use node4, or speed up the process npm install "git://github.com/ghostoy/node-serialport.git#nan1to2" and report your findings here
Weve got two windows issues that need reproduction and fixing:
- https://github.com/voodootikigod/node-serialport/issues/578#issuecomment-143591608
with [this test](https://gist.github.com/gnail/a1a2c0d11205c00286ab)
- https://github.com/voodootikigod/node-serialport/issues/578#issuecomment-144756809
with [this test](https://github.com/voodootikigod/node-serialport/pull/600/files)
Im contacting Chris about publishing and especially around all the changes to the travis file which also seems to be involved in publishing.
In my mind we merge a travis update so we can see whats up, then cherry pick or merge those PRs.
**But let me reiterate, were not going to be able to support nan2 (and thus node 4) until we get some windows testers and feedback**
Long term we're working on CI'ing this problem away (see https://github.com/nodejs/hardware/issues/13 ) but we're not there yet.
