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

Would it be possible to isolate global packages? #217

Open
fl0w opened this Issue Jan 15, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@fl0w

fl0w commented Jan 15, 2015

Not sure if this is of concern really. I've dealt with virtualenv previously and I loved setting up a specific environment with isolated global packages. Would this be of interest to n or is this out of scope? I'd imagine a feature like this would involve a number of breaking changes - a separate fork or even an entirely separate package.

My reasoning behind this feature/change is that with the introduction of io.js, it's of interest to me to have separate global versions installed of the same package depending on what environment I'm currently in.

I guess this ties in a bit into #212

@drschwabe

This comment has been minimized.

Show comment
Hide comment
@drschwabe

drschwabe Apr 30, 2015

Maybe whenever you npm install -g myglobalmodule n can somehow override the install path to:

n/versions/node/0.xx.x/node_modules/myglobalmodule

(and similar pattern for iojs)

drschwabe commented Apr 30, 2015

Maybe whenever you npm install -g myglobalmodule n can somehow override the install path to:

n/versions/node/0.xx.x/node_modules/myglobalmodule

(and similar pattern for iojs)

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