Build node 4.0 binaries - NODE_MODULE_VERSION 46 #1122
Comments
|
I can confirm that node some v4.0.0-pre with the new V8 builds and runs |
|
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. |
|
|
|
Ah, this is most likely due to nodejs/node-gyp#711 (comment); the fix has not been backported to |
|
Just a stupid download problem - try using |
|
You should drop pangyp in favor of node-gyp@3, it handles all these cases, including io.js & Node RCs. |
|
Oh, I missed it, sorry. Michał Gołębiowski |
|
A 3rd RC looks scheduled for release in the next 24hrs |
|
RC5 with working node-gyp is out: https://twitter.com/rvagg/status/641163073206681600 |
|
The final 4.0.0 is out. |
|
Hmm, I'm getting this right now. Is it looking for the wrong release? |
|
```
Cannot download "https://github.com/sass/node-sass/releases/download/v3.3.2/darwin-x64-46_binding.node": HTTP error 404 Not Found
```
We haven't released node 4.0 binaries yet?
|
|
Oh! I thought that was what @mzgol was talking about. Alright, I'll be patient. :3 |
|
But it's possible to compile it yourself, if you have a working C++11 compiler. Actually npm proceeds to the building stage after failed install. |
|
@saper It doesn't compile for me on OS X 10.11 public beta 6: |
|
I am having the same issue as @mzgol above on 10.10. Is there a fix coming soon for this? |
|
Ahh, ignore me. I must have had a broken (I knew I should have an enough modern compiler so the issue had to be sth else...) |
|
On Tue, 8 Sep 2015, Michał Gołębiowski wrote:
Ahh, ignore me. I must have had a broken `~/.node-gyp`, most likely because of trying experimental Node 4.0.0 binaries before. Removign that directory & running `npm install node-sass` again worked. :)
Michał,
I see you are running on a Mac - can you run `npm test` and see if you run into
#1127 ? I'd appreciate having your `config.gypi`
|
|
Hi, I got error installing node-sass on Node 4.0 (RTM). > node-sass@3.3.2 install /Users/nn/Documents/Projects/telfi/telfi-app/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/nn/Documents/Projects/telfi/telfi-app/node_modules/node-sass
> node scripts/build.js
Building: /Users/nn/.nvm/versions/node/v4.0.0/bin/node /Users/nn/Documents/Projects/telfi/telfi-app/node_modules/node-sass/node_modules/pangyp/bin/node-gyp.js rebuild --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp: /Users/nn/.node-gyp/4.0.0/common.gypi not found (cwd: /Users/nn/Documents/Projects/telfi/telfi-app/node_modules/node-sass) while reading includes of binding.gyp while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/Users/nn/Documents/Projects/telfi/telfi-app/node_modules/node-sass/node_modules/pangyp/lib/configure.js:346:16)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Darwin 14.5.0
gyp ERR! command "/Users/nn/.nvm/versions/node/v4.0.0/bin/node" "/Users/nn/Documents/Projects/telfi/telfi-app/node_modules/node-sass/node_modules/pangyp/bin/node-gyp.js" "rebuild" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /Users/nn/Documents/Projects/telfi/telfi-app/node_modules/node-sass
gyp ERR! node -v v4.0.0
gyp ERR! pangyp -v v2.3.2
gyp ERR! not ok
Build failed
npm ERR! Darwin 14.5.0
npm ERR! argv "/Users/nn/.nvm/versions/node/v4.0.0/bin/node" "/Users/nn/.nvm/versions/node/v4.0.0/bin/npm" "install" "node-sass"
npm ERR! node v4.0.0
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! 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 |
|
Hi, I got error installing node-sass on Node 4.0 (RTM).
Please read this issue before posting. We are not supporting Node 4.0 yet.
|
|
I did read the issue and know you don't support Node 4 yet. Just report the error I have with the RTM release and hope it helps somehow. If it doesn't, please just ignore. |
|
Sounds like some of there errors are just simply due to the us not having switched back to node-gyp. Even with a 404 when downloading binaries we should be falling back to a local compilations. |
|
@saper Hi. How much time it takes for node 4 integration? |
|
@hinell depends on the hourly rate offered! |
|
If you use OSX you should now have Node 4 support. |
|
@xzyfer it works, thanks a lot! |
|
\o/ :tada: |
|
If you use Linux you should now have Node 4 support. |
|
when should I expect |
|
Hopefully in the next couple hours. You can always follow our Twitter for more frequent updates. |
|
\o/ |
|
If you use Window you should now have Node 4 support. |
|
yep, it's working 👍 🎉 |
|
Yeah is running fine now, thanks @xzyfer ! |
|
@xzyfer thanks! |
|
We are listing Node v4.0 issues in this thread. If you find any other issues, please write the issue and add the following url. |
|
@yosuke-furukawa thanks, but we have no issues with Node v4 |
|
@xzyfer perfect :) |
|
Error on ubuntu 14.04 couldn't figure out if this was supported yet or not. Trying to do this in a dockerfile with an Ember project. Step 21 : RUN npm rebuild node-sass
Cannot download "https://github.com/sass/node-sass/releases/download/v3.2.0/linux-x64-46_binding.node": HTTP error 404 Not Found
Building: /usr/bin/nodejs node_modules/pangyp/bin/node-gyp rebuild --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library= |
|
@Master244 Please use node-sass@3.3.3 since 3.2.0 does not support node 4.x. This should be the version you install by the plain |
If you have the lastest version of node, the install will fail. According to this [comment] (sass/node-sass#1122 (comment)) by the package maintainer, bumping to ^3.3.3 will fix the issue.
|
my system is trying to fetch https://github.com/sass/node-sass/releases/download/v3.4.1/linux-x64-47_binding.node |
|
my system is trying to fetch https://github.com/sass/node-sass/releases/download/v3.4.1/linux-x64-47_binding.node
on the other hand it looks like there isn't any x86-47 How can i fix this problem
We don't support node v5.0.0 yet.
|
|
my system is trying to fetch https://github.com/sass/node-sass/releases/download/v3.4.1/linux-x64-47_binding.node
on the other hand it looks like there isn't any x86-47 How can i fix this problem
But you can try to compile node-sass (you need a recent C++ compiler installed to do that).
npm install will start compiling if it fails to download.
|
|
it looks like i need compile it manually because : gyp verb command rebuild [] npm ERR! node-sass@3.4.1 postinstall: |
You have to do what it says: Download the source code of the node engine If it doesn't work for you, just downgrade to node 4.x You will have the same problems with all node native add-ons, not only with node-sass. |
|
@saper @usta Note, thought, that this should be a problem only for manually compiled pre-releases (I suppose that's the case here). Compiling alphas, rcs etc. should work with newest node-gyp but doesn't for some reason, I reported it in #1224. Other native packages seem to be fine, only node-sass has problems here. |
node 4.0 will probably import V8 4.5, with minor changes to the V8 API (most probably not relevant to our module).
nanupgrade is not required.node 4.0 milestone
nodejs/node#2632 - import of V8
4.5.103.30nodejs/node#2678 -
NODE_MODULE_VERSIONbump to 46Binaries
Release
Release v3.3.3The text was updated successfully, but these errors were encountered: