Build node 4.0 binaries - NODE_MODULE_VERSION 46

[saper]

node 4.0 will probably import V8 4.5, with minor changes to the V8 API (most probably not relevant to our module). nan upgrade is not required.

node 4.0 milestone

nodejs/node#2632 - import of V8 4.5.103.30

nodejs/node#2678 - NODE_MODULE_VERSION bump to 46

Binaries

• OSX
• Linux 32bit
• Linux 64bit
• Windows 32bit
• Windows 64bit
• FreeBSD 32bit
• FreeBSD 64bit

Release

• Back port binaries to v3.3.2
• Release v3.3.3

[saper]

I can confirm that node some v4.0.0-pre with the new V8 builds and runs node-sass just fine. We just get a new set of modules with a number 46.

[xzyfer]

Cool, so we still need to generate binaries, but there's no real work required?

If we don't need to bump nan and do a new release we can just attach the new binaries to the current release.

[mgol]

node-sass doesn't compile for me in Node.js 4.0.0-rc.2 on OS X 10.11 (public beta 6):

$ node --version
v4.0.0-rc.2
$ npm --version
2.14.2
$ npm i node-sass
npm WARN engine node-sass@3.3.2: wanted: {"node":">=0.10.0"} (current: {"node":"4.0.0-rc.2","npm":"2.14.2"})
(...)
> node-sass@3.3.2 install /Users/mgol/_/node_modules/node-sass
> node scripts/install.js

Cannot download "https://github.com/sass/node-sass/releases/download/v3.3.2/darwin-x64-46_binding.node": HTTP error 404 Not Found

> node-sass@3.3.2 postinstall /Users/mgol/_/node_modules/node-sass
> node scripts/build.js

Building: /Users/mgol/.nvm/versions/node/v4.0.0-rc.2/bin/node /Users/mgol/_/node_modules/node-sass/node_modules/pangyp/bin/node-gyp.js rebuild --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp WARN install got an error, rolling back install
gyp ERR! configure error 
gyp ERR! stack Error: 404 status code downloading tarball
gyp ERR! stack     at Request.<anonymous> (/Users/mgol/_/node_modules/node-sass/node_modules/pangyp/lib/install.js:251:14)
gyp ERR! stack     at emitOne (events.js:82:20)
gyp ERR! stack     at Request.emit (events.js:169:7)
gyp ERR! stack     at Request.onRequestResponse (/Users/mgol/_/node_modules/node-sass/node_modules/pangyp/node_modules/request/request.js:1255:10)
gyp ERR! stack     at emitOne (events.js:77:13)
gyp ERR! stack     at ClientRequest.emit (events.js:169:7)
gyp ERR! stack     at HTTPParser.parserOnIncomingClient (_http_client.js:415:21)
gyp ERR! stack     at HTTPParser.parserOnHeadersComplete (_http_common.js:88:23)
gyp ERR! stack     at TLSSocket.socketOnData (_http_client.js:305:20)
gyp ERR! stack     at emitOne (events.js:77:13)
gyp ERR! System Darwin 15.0.0
gyp ERR! command "/Users/mgol/.nvm/versions/node/v4.0.0-rc.2/bin/node" "/Users/mgol/_/node_modules/node-sass/node_modules/pangyp/bin/node-gyp.js" "rebuild" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /Users/mgol/_/node_modules/node-sass
gyp ERR! node -v v4.0.0-rc.2
gyp ERR! pangyp -v v2.3.1
gyp ERR! not ok 
Build failed
npm ERR! Darwin 15.0.0
npm ERR! argv "/Users/mgol/.nvm/versions/node/v4.0.0-rc.2/bin/node" "/Users/mgol/.nvm/versions/node/v4.0.0-rc.2/bin/npm" "i" "node-sass"
npm ERR! node v4.0.0-rc.2
npm ERR! npm  v2.14.2
npm ERR! code ELIFECYCLE

npm ERR! node-sass@3.3.2 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the node-sass@3.3.2 postinstall script 'node scripts/build.js'.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/build.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/mgol/_/npm-debug.log

[mgol]

Ah, this is most likely due to nodejs/node-gyp#711 (comment); the fix has not been backported to pangyp yet (if ever).

[saper]

Just a stupid download problem - try using --nodedir=your-node-sourcedir and it will run fine. I am using rc.1 right now for testing and it works fine.

[mgol]

You should drop pangyp in favor of node-gyp@3, it handles all these cases, including io.js & Node RCs.

https://twitter.com/rvagg/status/641045378037510144

[xzyfer]

It's on the road map @mzgol #1124

We adopted pangyp to get around node-gyp's lack of iojs support.

[mgol]

Oh, I missed it, sorry.

Michał Gołębiowski

[xzyfer]

A 3rd RC looks scheduled for release in the next 24hrs

[fhemberger]

RC5 with working node-gyp is out: https://twitter.com/rvagg/status/641163073206681600
If we don't find any mayor blocker, the final v4.0.0 will be released in a few hours.

[mgol]

The final 4.0.0 is out.