Node 6: Failed at the node-sass@3.6.0 postinstall script 'node scripts/build.js' #1484
Comments
|
Something similar with Node 6 just upgraded: |
|
I'm seeing lots of JS+C stack traces & warnings when running node-sass 3.6.0 on Node 6.0.0, things like: and: |
|
Same issue as @ralekna.
|
|
Same as @mgol on Arch Linux with Node 6.0.0 and npm 3.8.7 |
|
Same issue |
|
Node 6 is not yet supported. This will be case for many native extensions Generally speaking dont expect everything to work when you're using the Same issue npm ERR! node-sass@3.6.0 postinstall:node scripts/build.js — You are receiving this because you are subscribed to this thread. |
|
@xzyfer It was more of a heads up, at least in my case. Most people on the bleeding edge aren't surprised by this sort of thing. |
|
+1, here is my stack trace: |
|
Thanks you we appreciate the heads up. These threads tend to devolve Once we have a fix it'll take a about a day to do a new release we because We'll hopefully have something by next week.
|
|
No worries @xzyfer It was purely informtive to let you guys know there's an issue in Node 6. I'm not expecting this to be resolved in the hour ;) |
|
If it's any help, related issue with fsevents module: fsevents/fsevents#127 and potential fix: https://github.com/strongloop/fsevents/pull/128/files Digging through the code, the error seems to originate from nan: https://github.com/sass/node-sass/blob/master/src/sass_types/map.cpp#L23 Related issue on nan repo: nodejs/nan#558 |
|
Same for me rm -f Release/sass.a && ./gyp-mac-tool filter-libtool libtool -static -o Release/sass.a Release/obj.target/libsass/src/libsass/src/ast.o Release/obj.target/libsass/src/libsass/src/base64vlq.o Release/obj.target/libsass/src/libsass/src/bind.o Release/obj.target/libsass/src/libsass/src/cencode.o Release/obj.target/libsass/src/libsass/src/color_maps.o Release/obj.target/libsass/src/libsass/src/constants.o Release/obj.target/libsass/src/libsass/src/context.o Release/obj.target/libsass/src/libsass/src/cssize.o Release/obj.target/libsass/src/libsass/src/emitter.o Release/obj.target/libsass/src/libsass/src/environment.o Release/obj.target/libsass/src/libsass/src/error_handling.o Release/obj.target/libsass/src/libsass/src/eval.o Release/obj.target/libsass/src/libsass/src/expand.o Release/obj.target/libsass/src/libsass/src/extend.o Release/obj.target/libsass/src/libsass/src/file.o Release/obj.target/libsass/src/libsass/src/functions.o Release/obj.target/libsass/src/libsass/src/inspect.o Release/obj.target/libsass/src/libsass/src/json.o Release/obj.target/libsass/src/libsass/src/lexer.o Release/obj.target/libsass/src/libsass/src/listize.o Release/obj.target/libsass/src/libsass/src/memory_manager.o Release/obj.target/libsass/src/libsass/src/node.o Release/obj.target/libsass/src/libsass/src/output.o Release/obj.target/libsass/src/libsass/src/parser.o Release/obj.target/libsass/src/libsass/src/plugins.o Release/obj.target/libsass/src/libsass/src/position.o Release/obj.target/libsass/src/libsass/src/prelexer.o Release/obj.target/libsass/src/libsass/src/remove_placeholders.o Release/obj.target/libsass/src/libsass/src/sass.o Release/obj.target/libsass/src/libsass/src/sass2scss.o Release/obj.target/libsass/src/libsass/src/sass_context.o Release/obj.target/libsass/src/libsass/src/sass_functions.o Release/obj.target/libsass/src/libsass/src/sass_util.o Release/obj.target/libsass/src/libsass/src/sass_values.o Release/obj.target/libsass/src/libsass/src/source_map.o Release/obj.target/libsass/src/libsass/src/to_c.o Release/obj.target/libsass/src/libsass/src/to_value.o Release/obj.target/libsass/src/libsass/src/units.o Release/obj.target/libsass/src/libsass/src/utf8_string.o Release/obj.target/libsass/src/libsass/src/util.o Release/obj.target/libsass/src/libsass/src/values.o |
|
Is there any way to suppress the warnings/stack traces? The |
|
check out https://github.com/sass/node-sass/releases
|
|
To my amazement I was able to build v3.6.0 on Node 6 with no issues. I've already uploaded the binaries for the v3.6.0 release to osx and linux users. Windows releases are trickier and complicated by missing support in AppVeyor (appveyor/ci#770). |
|
@xzyfer I cleaned npm & node-gyp caches & re-installed node-sass 3.6.0 on OS X 10.11.4 but I still see the long stack traces that I mentioned in my comment #1484 (comment). So the fact that it built doesn't seem to be enough. |
|
Yes, the same as @mgol here. |
|
node5.3 `> node scripts/install.js Cannot download "https://github.com/sass/node-sass/releases/download/v3.6.0/win32-x64-48_binding.node":` it is 404 |
|
@mgol I understand. Yes you'll still get annoying stack traces, but for those who cannot build locally they'll at least now be able to install node-sass. |
|
@mgol to be clear, our test suite passes with the Node 6 with binaries. The stack traces are an annoyance, no more. |
|
@xzyfer They might be a mere annoyance however webpack throws an error with a similar stack trace and crashes |
|
@alexeygolev that's likely because webpack's watcher is broken on Node 6. Most filesystem watches are native extensions like node-sass. |
|
The warnings can be silenced with |
OK, thanks for the info! |
|
Confirmed my initial issue is now resolved. My build is passing on Travis. |
|
Confirmed, thanks for the hard work.
|
ghost
mentioned this issue
|
Any possible to backport this fix to node-sass 3.3? node-sass 3.4 introduces breaking changes for our older SASS project, but we are moving onto a new project and want to use node 6. Our only option right now is to install the python executable and c++ binaries but it would be awesome if this update was back-ported to 3.3 |
|
@egucciar unfortunately it is not possible to back port this change because it's in the native code that talks to LibSass. |
|
With Node 6.2.1 |
|
@Yimiprod fixed in v3.7.0 |
|
Still having the same issue even with node-sass 3.7.0 |
|
I'm having issues with 3.8.0, I think. Ubuntu, Node 6.3.1
|
|
Please read the documentation on how to file a bug. Saying "it doesn't On 6 Aug 2016 5:11 AM, "Alexander Harding" notifications@github.com wrote:
|
|
@xzyfer seems like we have a new catch-all bug here. I wonder if there is a way to get a compiler output in a way that npm puts it in the log properly. Also maybe we should provide a user friendly summary why scripts/install.js failed AGAIN, after build.js failure. Just some random thoughts how to deal with the reports like those above. |
|
@saper I think we already do that. The above screen shot is strange because it's void of the usual output. |
|
failing on ubuntu sh: 1: node: not found npm ERR! node-sass@3.8.0 install: npm ERR! Please include the following file with any support request: |
|
I am trying to build an electron app that will run gulpfiles from a GUI. However, since we use sass, I am now getting this error with both node versions 4.5.0 and 6.8.1. I was running 4.5.0 and our gulpfiles worked fine from the CL. I updated to 6.8.1 and started getting this same error message. I ran |
|
This a known bug in electron - electron/electron#6318 & electron/electron#5851 |
|
the same issue |
|
same :( |
|
@owndann I fixed use "npm rebuild node-sass " |
|
I was having this issue on OSX: Node version Seems to happen after upgrading nodejs. Thanks! |
and others
Looks like there's an issue with the newly released Node 6.0.0
The text was updated successfully, but these errors were encountered: