execSync
execSync copied to clipboard
mgutz
Cannot find module './build/Release/shell'
After installing with npm install execSync I got Cannot find module './build/Release/shell' error.
I had to go into the node_modules directory and build it myself passing the flag --python python2 to the node-gyp rebuild command.
I have the same problem!
The problem is that your system doesn't make the build:
[execsync v1.0.2] Attempting to compile native extensions.
[execSync v1.0.2]
Native code compile failed!!
In my case the problem appear today, yesterday all worked fine and the repository hasn't been updated. ¿?
Hi,
In my case:
- download the proyect
- do
node-gyp rebuild - see the message error :)
Agreeing to the Xcode/iOS license requires admin privileges, please re-run as root via sudo.
damm!
We hit this too. There was no way we could fix. Running node-gyp did not fix the problem.
Digging a little on the net I've found that this is affecting only guys that are using Python 3.x as their default python executable ( see https://github.com/TooTallNate/node-gyp/issues/526 and https://github.com/atom/atom/issues/1933 ). To fix this issue ( call it a workaround) you should do this on the project you're having this issue:
npm config set python /usr/bin/python2.7
npm install
Make sure that you're having Python 2 installed as a package in your distro ( my solution is based on Ubuntu 14.10 ).
Have fun :)
@julianxhokaxhiu unfortunately, this doesn't solved my problem.
Besides that, the most annoying thing about that bug is that it appears out of a sudden. Yesterday everything worked perfectly. Can everyone come up with an idea for an explanation?
@scheffield are you sure? For me it worked also two days ago on Arch Linux where I did my new dev server (same error, same fix and now working awesome).
Try to remove your node_modules folder after you set the npm config for python :)
Finally make sure (obviously) that python 2 is installed and running on your machine...
We resolved this a short time ago. Turned out my coworker who was hitting this problem had a rogue, custom build of make in his path. Sorry for the confusion.
Also getting this issue, and I'm running Python 2.7.6.
Running node-gyp rebuild doesn't work for me (command not found).
This also did not fix the issue:
npm config set python /usr/bin/python2.7
npm install
Also running in this issue. I have tried all of the suggestions above and still no luck. Any other suggestions? Much appreciated.
I am facing the same issue. Tried the above suggestions but of no help. I am using OSX 10.9.4. Need help urgently. That will be much appreciated.
I would suggest to use exec-sync from now on, compatible with nodejs 0.12.x and anyway it doesn't depend on libc, python or stuff like this :)
I am still getting the same error even after using sudo npm install exec-sync
The error is:
events.js:72
throw er; // Unhandled 'error' event
^
Error: Cannot find module './build/Release/shell'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.
Any other solution to it?
Clean reinstall NPM and remove all node_modules folders. Then just run again npm install :)
@webpolis Using a 3rd party library, grunt-favicons otherwise I would. Still looking, let you know if I find anything.
These are some alternatives:
- Native for: >v0.12 https://nodejs.org/api/child_process.html#child_process_child_process_execsync_command_options
- https://github.com/arturadib/shelljs
It may be worth noting that you can have issues using node v0.12 instead of v0.10 for example, try downgrading it using nvm.
Easily solved on a Mac: run sudo make to cause Xcode to prompt you to agree to the license terms, then run npm install execSync again.
