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!

@olanod

I had same problem than @olanod. Solved by simple 'node-gyp rebuild'

We hit this too. There was no way we could fix. Running node-gyp did not fix the problem.

Also affects me

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 nodejs/node-gyp#526 and atom/atom#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

@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

@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. (/Users/sabreena/.nvm/v0.10.24/lib/node_modules/generator-drupal-theme/node_modules/execSync/index.js:30:11)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)

Any other solution to it?

Clean reinstall NPM and remove all node_modules folders. Then just run again npm install :)

No solution works.

No solution works to me too

No solution here either.

Only solution is switching to https://www.npmjs.com/package/exec-sync

@webpolis

@webpolis Using a 3rd party library, grunt-favicons otherwise I would. Still looking, let you know if I find anything.

@webpolis

@webpolis Wound up just forking and updating manually.

These are some alternatives:

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.

@aclowes

@aclowes' solution worked for me. Thanks pal! 👍

@aclowes

@aclowes thanks, that worked for us.

@mgutz

Time to close this @mgutz ?

Navigation Menu

Repository navigation

Cannot find module './build/Release/shell' #27

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Cannot find module './build/Release/shell' #27

Description

Activity

Kikobeats commented on Oct 1, 2014

Kikobeats commented on Oct 1, 2014

bdavidxyz commented on Oct 10, 2014

n8agrin commented on Oct 27, 2014

mrfelton commented on Nov 26, 2014

julianxhokaxhiu commented on Nov 28, 2014

scheffield commented on Jan 9, 2015

julianxhokaxhiu commented on Jan 10, 2015

n8agrin commented on Jan 12, 2015

cperryk commented on Feb 3, 2015

ccgroupdev commented on Feb 10, 2015

sabreena commented on Feb 18, 2015

julianxhokaxhiu commented on Feb 18, 2015

sabreena commented on Feb 19, 2015

julianxhokaxhiu commented on Feb 19, 2015

webpolis commented on Mar 22, 2015

megatolya commented on Mar 22, 2015

sgarbesi commented on Mar 23, 2015

webpolis commented on Mar 23, 2015

sgarbesi commented on Mar 23, 2015

sgarbesi commented on Mar 23, 2015

luishdez commented on Mar 31, 2015

cphyc commented on May 19, 2015

aclowes commented on Nov 10, 2015

fmquaglia commented on Feb 5, 2016

rvergis commented on Feb 5, 2016

julianxhokaxhiu commented on Sep 16, 2018

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions