node-sass and node v0.12.0

[TrollWarlord]

I have node 0.12.0 and everytime I try to install the node app

I've tried to install/reinstall node-sass and try to run the everything I'm getting:

throw new Error('libsass bindings not found. Try reinstalling node-sass?

[am11]

Please provide some more information:

If you are using Linux/Mac, follow these steps, make a gist and share the link.

For Windows run these commands and share the output gist link.

[RobLoach]

Ran into similar issues. Deleting ~/.npm and node_modules fixed it.

[pepelsbey]

@am11, I have the same problems using node-sass with iojs, see my gist: https://gist.github.com/pepelsbey/45b0d27dec931d03b90b

[am11]

@pepelsbey, io.js v1.4.1 is not supported by node-sass v2.0.1.

You can downgrade io.js to v1.2.0 to make it work.

See #730.

[pepelsbey]

Ok, it works now after installing v1.2.0 — https://iojs.org/dist/v1.2.0/iojs-v1.2.0.pkg
Thank you

[am11]

@pepelsbey, you might want to take a look at https://github.com/creationix/nvm, a version manager for node.js which makes it easy to switch between node.js/io.js versions.

[saper]

Ran into this today as well. I guess 9bd034c might fix this, moving pangyp from dev to runtime dependencies.

https://gist.github.com/saper/8c1cf488d4bf9034900d

This is on FreeBSD 10.0, amd64.

Using npm install sass/node-sass takes me further and fails on the fact that FreeBSD 10.x has now only clang by default:

https://gist.github.com/saper/d5de2c2228630c12643f

[am11]

@saper, actually that is a fallback option in case the prebuild binary is not compatible with the target OS, in which case our build script fallbacks to manual build (which requires pangyp, python 2.7.x and g++ 4.6+ / VS2013+). So our intention is to prevent that fallback from happening at install-time.

Starting next release, we are using better approach to detect the runtime, which will expand the binary compatibility with frequently incrementing io.js version. See #694.

[saper]

Yes, it is a fallback because I cannot see FreeBSD binaries there.

[am11]

That's in our v3 milestone, the upcoming version of node-sass. ;)

FreeBSD and Oracle Solaris binaries.

Sent from my Windows Phone

---

From: Marcin Cieślakmailto:notifications@github.com
Sent: ‎3/‎3/‎2015 22:57
To: sass/node-sassmailto:node-sass@noreply.github.com
Cc: Adeel Mujahidmailto:adeelbm@outlook.com
Subject: Re: [node-sass] node-sass and node v0.12.0 (#721)

Yes, it is a fallback because I cannot see FreeBSD binaries there.

---

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

[saper]

Thank you, I managed to compile node-sass for v2.0.1 using

env CC=clang CXX=clang++ GYP_DEFINES="clang=1" npm install

I have posted the resulting binary into sass/node-sass-binaries#46

[am11]

Awesome!

[framerate]

@am11 I'm auditing my workflow and different versions of iojs for deployment. When do you guys plan on having the v3 version? I won't hold you to it, but are we talking days? weeks? months? years?

Thanks!

[am11]

@framerate, cross referencing: #710 (comment).

[am11]

The pre-release v3.0.0-pre is out. See the breaking changes in README.

npm install node-sass@3.0.0-pre

To see the runtime coverage matrix, see node-sass-binaries readme: https://github.com/sass/node-sass-binaries/#node-sass-binaries.

Let us know what you think on https://gitter.im/sass/node-sass.

Closing this due to inactivity.

@TrollWarlord, feel free to open it with proper reproduction steps. See our Bug Reporting guidelines: https://github.com/sass/node-sass/blob/master/CONTRIBUTING.md#bug-reports.