Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove dependency on execsync? #12

Closed
davidham opened this issue Apr 22, 2015 · 2 comments
Closed

Remove dependency on execsync? #12

davidham opened this issue Apr 22, 2015 · 2 comments

Comments

@davidham
Copy link

When I run 'yo poole' I get this message:

module.js:338
    throw err;
    ^
Error: Cannot find module './build/Release/shell'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/usr/local/lib/node_modules/generator-poole/node_modules/execSync/index.js:30:11)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)

This appears to be an error related to execSync. I don't know what execSync does, but apparently it used to be a separate module and now it's built into Node? Here's a similar issue from another project:

percyhanna/mincer-ruby-sass#2

See also #11. Would removing this dependency solve the issue?

@meherhowji
Copy link

Faced the same problem, then after spending some around with it on execSync repo, i figured that the execSync name being camelcased in not allowed in node 0.12.0. One way to fix would be to update the dependecy to sync-exec or similar OR downgrade our local node to < 0.12.0

Using nvm can come in handy for such kind of situations. https://github.com/creationix/nvm

@johnslipper
Copy link

Have had the same problem myself today, would be great to remove the dependancy as have had issues using nvm and going back to < 0.12.0 is not really an option for me.

@davidham davidham closed this as completed Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants