chrisa / node-dtrace-provider

Native DTrace probes for node.js apps
Other
321 stars 68 forks source link

Migration from node 0.8 to 0.10 by invoking npm rebuild fails with ENOENT #32

Closed cobracmder closed 10 years ago

cobracmder commented 11 years ago

When migrating from node 0.8 to 0.10 with dtrace-provider already installed and user is call npm rebuild, rebuild will fail with ENOENT while looking for node-waf.

Might need to add additional properties to package.json to explicitly call node-gyp clean or something.

Log:

100 verbose rebuild path, id [ '/Users/los/node_modules/dtrace-provider',
100 verbose rebuild   'dtrace-provider@0.2.8' ]
101 silly rebuild set [ '/Users/los/node_modules/dtrace-provider' ]
102 silly exec node-waf "clean"
103 silly node-waf,clean,/Users/los/node_modules/dtrace-provider spawning
104 error Error: spawn ENOENT
104 error     at errnoException (child_process.js:945:11)
104 error     at Process.ChildProcess._handle.onexit (child_process.js:736:34)
105 error If you need help, you may report this log at:
105 error     <http://github.com/isaacs/npm/issues>
105 error or email it to:
105 error     <npm-@googlegroups.com>
106 error System Darwin 12.3.0
107 error command "node" "/usr/local/bin/npm" "rebuild" "dtrace-provider"
108 error cwd /Users/los
109 error node -v v0.10.0
110 error npm -v 1.2.14
111 error syscall spawn
112 error code ENOENT
113 error errno ENOENT
114 verbose exit [ 1, true ]
tjfontaine commented 10 years ago

I presume this was because of some wscript priority at some point, I'm fairly certain this is not a problem anymore