Add Node v6.0.0 support

[KidLinus]

When using node v6.0.0 with node-sass and webpack i get the following error:

webpack --config webpack.config.dev.js --watch

Hash: 9e5059f15d2b9c2485b1
Version: webpack 1.13.0
Time: 1991ms
Asset Size Chunks Chunk Names
app.js 1.13 MB 0 [emitted] main
[0] multi main 28 bytes {0} [built]
+ 285 hidden modules

ERROR in Node Sass does not yet support your current environment: OS X 64-bit with false
For more information on which environments are supported please see:
TODO URL
@ ./src/style/main.scss 4:14-121

[lorem--ipsum]

I think it's done but needs a release, looking at the code.

[xzyfer]

We're blocked on appveyor adding mode 6 support.
On 29 Apr 2016 7:25 PM, "Sébastien" [email protected] wrote:

I think it's done but needs a release, looking at the code.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#1504 (comment)

[jhough10]

@xzyfer is there any info on when appveyor will add mode 6 support?

[xzyfer]

You know as much as I do
On 30 Apr 2016 12:49 AM, "Justin Hough" [email protected] wrote:

@xzyfer https://github.com/xzyfer is there any info on when appveyor
will add mode 6 support?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#1504 (comment)

[lorem--ipsum]

Meanwhile, I did that (dirty as hell but who cares) to keep on working :

• change the locally installed files according to b0e1e1b
• run npm rebuild node-sass

Enjoy (especially if you like flooded console outputs).

[jhough10]

@lorem--ipsum yeah, the stack traces are a good read especially when you have to find errors. 👍

[glen-84]

Not sure if this is relevant: https://twitter.com/appveyor/status/725385312843632640

[xzyfer]

Yeap we're on it. We currently have s failing Windows test with node 6 in
CI only. Going to dig into it in the next 24hrs.
On 30 Apr 2016 5:02 AM, "Glen" [email protected] wrote:

Not sure if this is relevant:
https://twitter.com/appveyor/status/725385312843632640

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#1504 (comment)

[JaLuxe]

I just failed installing on Windows 64 bit.

It seems as if it is tried to download a non-existing .node file "..x-64-48binding.node"

npm 3.8.8
node.js v 6.00

"Cannot download "https://github.com/sass/node-sass/releases/download/v3.4.2/win32-x64-48binding.node":

HTTP error 404 Not Found"

Is there a way to install an older version to get it running until it's fixed?
Thank you in advance for your efforts.

JaLuxe

ps. Sorry if this comment should be misplaced

[Robert-Janagap]

@JaLuxe same here problem

[byCedric]

@JaLuxe Yes, the 48 version of the bindings are not released. Therefore it tries to make it from the source I think. This is because version 48, or node v6.0.0, is not in the latest release. Let's hope everybody is as awesome as usual, and its fixed asap :).

The best workaround for now is just use node v5.x.x...

[ketsugi]

I updated to Node 6.0.0 and now I'm getting these huge stack traces whenever the sass task runs. Am I right to understand that these are not errors and I can ignore them?

[xzyfer]

For those playing along at home we've spent the last 48hrs debugging a bug in Node 6 (nodejs/node#6500) which is blocking us.

[robjens]

Well here it builds, it is just a deprecation warning (albeit annoying one) and it should be node 7 ready anyway. When I run gulp it spits out tons of JS/C stack dump but for the rest everything works.

[PepijnSenders]

Is there any way to silence these stack traces?

[xzyfer]

[email protected] has been released.

[Muralilive]

'npm install gulp-sass ' this work for me