Consider supporting npm install -g awsbox #71

Open
ryanseys opened this Issue Jun 3, 2013 · 4 comments

Comments

Projects
None yet
3 participants
Member

ryanseys commented Jun 3, 2013

Rather than calling the executable from node_modules, allow a global installation of the executable?

Contributor

lloyd commented Jun 3, 2013

There shouldn't be anything to prevent this right now, its just not advertised in documentation because things are more likely to break on upgrade.

Ryan Seys notifications@github.com wrote:

Rather than calling the executable from node_modules, allow a global installation of the executable?


Reply to this email directly or view it on GitHub:
#71

Member

ryanseys commented Jun 3, 2013

This is true. I spoke too soon. Considering you don't want things to break on upgrade, should you then not suggest they save their devDependency with version "*"? I realize that --save-dev will save the dependency in package.json with a "~0.x.x" version number but this isn't initially suggested when they run npm install awsbox.

If installation is local to the package to prevent things from breaking in the future, I would suggest they save their dependencies with a version number rather than "*".

Member

ryanseys commented Jun 3, 2013

I realize I'm now just nitpicking but it was unclear as to why -g is not suggested or mentioned.

You could also opt for an apporach similar to grunt.js. They have split their command line interface and tools to prevent stuff from breaking. It's the best of both worlds imho.

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