Skip to content

new(?) npm install script breaking nodeenv #2

@jeremyBanks

Description

@jeremyBanks

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.

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions