Troubles with Node 0.12

[arthurvr]

Having this in both travis and locally.

$ node --version
v0.12.0
$ npm --version
2.5.1
$ nvm --version
0.23.3

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> (/home/travis/build/h5bp/html5please/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)

[mntnoe]

Found the following in the npm install output:

> node install.js

[execsync v1.0.2] Attempting to compile native extensions.
[execSync v1.0.2]
    Native code compile failed!!

Edit: Node >= 0.11 has child_proces.execFileSync, see #36. Perhaps the README should be updated?

[mgutz]

There is a PR that solved this but unfortunately npm no longer allows me to publish updates due to the project having a camelCased title.

[marten-seemann]

So what is the solution? How do I make execSync build again?

[arthurvr]

There is a PR that solved this but unfortunately npm no longer allows me to publish updates due to the project having a camelCased title.

@mgutz Well then, it would be nice if you could change the title :)

[nottoseethesun]

I was able to workaround by using a different package instead, sync-exec .

[miguel76]

According to the npm site there are more than one hundred packages depending from this one, and these are just the direct dependencies.
Is not possible to contact npm and ask if there is some workaround to the camelCase problem? Like automatic redirection to a new project with a permitted name, or redirection to "sync-exec". They should offer some solution to the problem.