Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Can't install node-sass #123

Closed
brzpegasus opened this issue Jul 12, 2013 · 14 comments
Closed

Can't install node-sass #123

brzpegasus opened this issue Jul 12, 2013 · 14 comments

Comments

@brzpegasus
Copy link

Running npm install node-sass gives me this error:

$ npm install node-sass
npm http GET https://registry.npmjs.org/node-sass
npm http 200 https://registry.npmjs.org/node-sass
...
npm http GET https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.2.tgz
npm http 200 https://registry.npmjs.org/wordwrap/-/wordwrap-0.0.2.tgz

> [email protected] install c:\Users\edeblois\Projects\test\node_modules\node-sass
> node rebuild.js


events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:980:11)
    at Process.ChildProcess._handle.onexit (child_process.js:771:34)
unbuild [email protected]
npm ERR! weird error 8
npm ERR! not ok code 0
@brzpegasus
Copy link
Author

Forgot to mention I'm seeing this on Windows (7) with Node 0.10.13.

@brzpegasus
Copy link
Author

Actually, this commit cfe6e89 removes rebuild.js. It must not have been pushed to NPM? Or am I missing something?

@brzpegasus
Copy link
Author

Hmm, no. Checked out node-sass from master and ran npm install to see. Now I'm getting too many fatal errors with node-gyp:

Warning: Missing input files:
c:\Users\edeblois\Apps\node-sass\build\..\libsass\document.cpp
c:\Users\edeblois\Apps\node-sass\build\..\libsass\context.cpp
...
c:\Users\edeblois\Apps\node-sass\build\..\libsass\eval_apply.cpp
c:\Users\edeblois\Apps\node-sass\build\..\libsass\sass_interface.cpp
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
  sass_context_wrapper.cpp
  binding.cpp
  constants.cpp
  eval_apply.cpp
c1xx : fatal error C1083: Cannot open source file: '..\libsass\constants.cpp': No such file or directory [c:\Users\edeblois\Apps\node-sass\build\binding.vcxproj]
c1xx : fatal error C1083: Cannot open source file: '..\libsass\eval_apply.cpp': No such file or directory [c:\Users\edeblois\Apps\node-sass\build\binding.vcxproj]
...
C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include\xlocale(336): warning C4530: C++ exception handler used,
 but unwind semantics are not enabled. Specify /EHsc (..\binding.cpp) [c:\Users\edeblois\Apps\node-sass\build\binding.vcxproj]
c:\users\edeblois\apps\node-sass\sass_context_wrapper.h(1): fatal error C1083: Cannot open include file: 'libsass/sass_interface.h': No such file or directory (..\binding.cpp) [c:\Users\edeblois\Apps\node-sass\build\binding.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (c:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:267:23)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:789:12)
gyp ERR! System Windows_NT 6.1.7601

I guess I'll just wait to hear back from someone =).

@brzpegasus
Copy link
Author

For 0.5.3, it looks like this commit made it fail on Windows: dd6fcd0
because of this Node issue: nodejs/node-v0.x-archive#5841

@andrew
Copy link
Contributor

andrew commented Jul 12, 2013

I'll get this reverted and release a new version this evening, sorry for the issue.

@andrew
Copy link
Contributor

andrew commented Jul 12, 2013

I've just published node-sass v0.5.4 which reverts the building changes, should hopefully fix this.

@andrew andrew closed this as completed Jul 12, 2013
@brzpegasus
Copy link
Author

It does indeed. Thanks!

@benfrain
Copy link

Unsure if this is related. On one machine, using node-sass 0.6.1 as a dependency of Grunt installed fine with npm install. However, on another, it hangs on node rebuild.js. Left it 10+ minutes and nothing happens.

If I revert to 0.6.0 the node rebuild.js part completes fine (OSX 10.8 in both cases).

@andrew andrew reopened this Jul 31, 2013
@benfrain
Copy link

Beg your pardon. If I revert to 0.5.3 it completes fine. Reverting to 0.6.0 seems to suffer the same issue (prob something I'm doing mind). I'm using Node 0.10.15.

@andrew
Copy link
Contributor

andrew commented Jul 31, 2013

I'll take a look into it, are you on a mac or linux?

@benfrain
Copy link

Mac OS X 10.8 in both cases. Different physical systems though e.g. not using Virtual Machines. Once machine flew through and worked as expected. Only one seems to have this issue so it's probable I'm doing something stupid (Grunt newb). Perhaps wait until someone else reports similar issue before wasting any time on it. I'm merely changing dependency from:

{
  "name": "grunt-test",
    "version": "0.0.1",
    "devDependencies": {
        "grunt": "~0.4.1",
        "grunt-contrib-watch": "~0.4.3",
        "grunt-bake": "~0.1.0",
        "sass-node": "0.5.3",
        "grunt-sass": "~0.6.0",
        "grunt-contrib-concat" : "~0.3.0",
        "grunt-contrib-copy" : "~0.4.1",
        "grunt-play" : "~0.1.0",
        "grunt-contrib-connect" : "~0.3.0"
    }
}

To:

{
  "name": "grunt-test",
    "version": "0.0.1",
    "devDependencies": {
        "grunt": "~0.4.1",
        "grunt-contrib-watch": "~0.4.3",
        "grunt-bake": "~0.1.0",
        "sass-node": "~0.6.1",
        "grunt-sass": "~0.6.0",
        "grunt-contrib-concat" : "~0.3.0",
        "grunt-contrib-copy" : "~0.4.1",
        "grunt-play" : "~0.1.0",
        "grunt-contrib-connect" : "~0.3.0"
    }
}

@andrew
Copy link
Contributor

andrew commented Jul 31, 2013

I did notice it last night as well, but then when i ran it again it sorted itself out, doesn't seem to happen on travis.

Hopefully I'll get time to look into it tonight.

@andrew
Copy link
Contributor

andrew commented Aug 1, 2013

Just released v0.6.2 which should fix this

@andrew andrew closed this as completed Aug 1, 2013
@benfrain
Copy link

benfrain commented Aug 1, 2013

All working great now, thanks for your efforts. :)

jiongle1 referenced this issue in scantist-ossops-m2/node-sass Apr 7, 2024
Yeah, that's an old file that I was using during development ... thanks for the patch!

[test_node_factory.cpp] Remove unused unordered_map include.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants