new(?) npm install script breaking nodeenv #2

jeremyBanks opened this Issue May 1, 2011 · 2 comments


None yet
2 participants

I noticed that initializing a new nodeenv was failing. When I ran with --verbose, I saw that this was because the npm install script is asking

This script will find and eliminate any shims, symbolic
links, and other cruft that was installed by npm 0.x.

Is this OK? enter 'yes' or 'no' 

and nodenv wasn't answering. The user can manually enter yes, but piping yes | nodeenv ... doesn't work.

I'm using npm 0.3.0 (from PyPi).

@ghost ghost assigned ekalinin May 2, 2011


ekalinin commented May 2, 2011

Thanks! Fixed in 987d08c.
Please upgrade to the latest version of the nodeenv (0.3.4) via pypi.

@ekalinin ekalinin closed this May 2, 2011

ekalinin pushed a commit that referenced this issue Aug 14, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment