Error running "npm install css-sprite" with node 0.12.0

[ricardomasao]

When I run "npm install", I'm getting erros:

fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make: *** [Release/obj.target/pathwatcher/src/main.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1067:12)
gyp ERR! System Darwin 14.0.0
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/ricardoshigeoka/Jobs/Brastemp/Menu/node_modules/css-sprite/node_modules/gaze
gyp ERR! node -v v0.12.0
gyp ERR! node-gyp -v v1.0.2
gyp ERR! not ok

npm ERR! Darwin 14.0.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "css-sprite"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE

npm ERR! gaze@0.6.4 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the gaze@0.6.4 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the gaze package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls gaze
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:

I'm running on Mac OSX Yosemite.

node version 0.12.0

[Moinax]

+1

[computersarecool]

+1

[CREEATION]

+1. This is because gaze@0.6.4 isn't compatible with node version 0.12.0, see https://github.com/shama/gaze/issues/175 & https://github.com/shama/gaze/issues/178

[alexkaraman85]

@CREEATION - Also have this issue with node 0.10.34

[INFO] > lwip@0.0.6 install C:\Workspace\code\main\node_modules\css-sprite\node_modules\lwip [INFO] > node-gyp rebuild [INFO] [INFO] [INFO] C:\Workspace\code\main\node_modules\css-sprite\node_modules\lwip>node "C:\Workspace\code\main\node\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild [INFO] npm ERR! Windows_NT 6.1.7601 [INFO] npm ERR! argv "C:\Workspace\code\main\node node" "C:\Workspace\code\main\node\npm\bin npm-cli.js" "install" "--color=false" [INFO] npm ERR! node v0.10.34 [INFO] npm ERR! npm v2.1.6 [INFO] npm ERR! code ELIFECYCLE [INFO] [INFO] npm ERR! gaze@0.6.4 install: node-gyp rebuild [INFO] npm ERR! Exit status 1 [INFO] npm ERR! [INFO] npm ERR! Failed at the gaze@0.6.4 install script. [INFO] npm ERR! This is most likely a problem with the gaze package, [INFO] npm ERR! not with npm itself. [INFO] npm ERR! Tell the author that this fails on your system: [INFO] npm ERR! node-gyp rebuild

[alexkaraman85]

@aslansky

Is it possible to downgrade to gaze@0.5.x until @shama fixes this?

https://github.com/shama/gaze/issues/110#issuecomment-61302737

[judewang]

@alexkaraman85

You can try using node v0.10.31, it worked for me, too.

[ricardomasao]

Downgraded to v.0.10.31 and didn't work

> gaze@0.6.4 install /Users/ricardoshigeoka/Jobs/Brastemp/Menu/node_modules/css-sprite/node_modules/gaze
> node-gyp rebuild

gyp WARN EACCES user "root" does not have permission to access the dev dir "/Users/ricardoshigeoka/.node-gyp/0.10.31"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/Users/ricardoshigeoka/Jobs/Brastemp/Menu/node_modules/css-sprite/node_modules/gaze/.node-gyp"
  CXX(target) Release/obj.target/pathwatcher/src/main.o
  CXX(target) Release/obj.target/pathwatcher/src/common.o
  CXX(target) Release/obj.target/pathwatcher/src/handle_map.o
../src/handle_map.cc:41:3: warning: 'NanDispose' is deprecated [-Wdeprecated-declarations]
  NanDispose(iter->second); // Deprecated, use NanDisposePersistent when v0.12 lands
  ^
../node_modules/nan/nan.h:612:48: note: 'NanDispose<v8::Value>' has been explicitly marked deprecated here
  template<class T> static NAN_DEPRECATED(void NanDispose(
                                               ^
../node_modules/nan/nan.h:149:65: note: expanded from macro 'NAN_DEPRECATED'
# define NAN_DEPRECATED(declarator) __attribute__((deprecated)) declarator
                                                                ^
../src/handle_map.cc:48:5: warning: 'NanDispose' is deprecated [-Wdeprecated-declarations]
    NanDispose(iter->second); // Deprecated, use NanDisposePersistent when v0.12 lands
    ^
../node_modules/nan/nan.h:612:48: note: 'NanDispose<v8::Value>' has been explicitly marked deprecated here
  template<class T> static NAN_DEPRECATED(void NanDispose(
                                               ^
../node_modules/nan/nan.h:149:65: note: expanded from macro 'NAN_DEPRECATED'
# define NAN_DEPRECATED(declarator) __attribute__((deprecated)) declarator
                                                                ^
2 warnings generated.
  CXX(target) Release/obj.target/pathwatcher/src/pathwatcher_mac.o
  SOLINK_MODULE(target) Release/pathwatcher.node
  SOLINK_MODULE(target) Release/pathwatcher.node: Finished
npm ERR! cb() never called!
npm ERR! not ok code 0

[alexkaraman85]

@ricardomasao - tried today as well and 0.10.31 did not change anything for me. Still getting the same issue.

[ventrebleu]

+1

[cmnstmntmn]

+1

[cmnstmntmn]

you may try an older release v0.10.29 works for me

[iboozyvoozy]

+1

[ricardomasao]

Tryed v0.10.29 and worked!

Thanks @cmnstmntmn

[denisborovikov]

Downgrade doesn't resolve a problem. Current version of node.js is 0.12.0 and css-sprite should works on it.

@ricardomasao Please, reopen an issue.

[ricardomasao]

I closed the issue as this solves the errors reported initially. I think the right thing would be to open a new issue reporting the error in node v0.12.0. Would be clearer for everyone. @denisborovikov

[denisborovikov]

@ricardomasao The reason why you've got this error was node.js v. 0.12.0 and probably Mac OSX Yosemite (as in my case) , so the issue you've opened is what we need. You may just rename it to make more clear description.

[alexkaraman85]

I'm with @denisborovikov, downgrading to an older version of Node.js is not a fix to this issue, but a work around.

[aslansky]

should be resolved with 0.9.6

[Moinax]

It's working, thanks :)

[paulstatezny]

On 0.9.0 I was able to resolve this issue by rolling back Node to 0.10.29, per the comments above.

[zjhiphop]

Mac + NodeJS v5.3.0

+1