-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
I think npm global packages should be installed in it's own directory #1220
Comments
I wonder if removing https://github.com/lukesampson/scoop/blob/master/bucket/nodejs.json#L18 would do the trick. Perhaps we would also need to add an environment variable to tell npm to look in ~/appdata/roaming/npm as well. Are there any Node experts listening that can help with this? Also, I think @rrelmy is looking at adding special |
I believe you can set the prefix for where packages get installed.
…On Tue, 17 Jan 2017, 18:26 Luke Sampson ***@***.***> wrote:
I wonder if removing
https://github.com/lukesampson/scoop/blob/master/bucket/nodejs.json#L18
would do the trick. Perhaps we would also need to add an environment
variable to tell npm to look in ~/appdata/roaming/npm as well.
Are there any Node experts listening that can help with this?
Also, I think @rrelmy <https://github.com/rrelmy> is looking at adding
special conf directories that would be maintained between updates (see
#1185 <#1185>). So that might
help with this in the long term.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1220 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA0Qgj7TyHHC2Rn10VjajAAC4aHd8H_8ks5rTG0ygaJpZM4Lk0Qa>
.
|
I created a
|
I think using appdata for the packages leads to problems like #847 Using a dedicated data directory inside scoop maybe the best idea. I couldn't start with the change from #1185, but I can do it this evening. Do mysql and mariadb suffer from the same problem? |
Looking way back at #126 and an aborted attempt at a similar thing, it looks like MariaDB, Vagrant, Nginx and Apache suffer from similar problems and would benefit. @deevus actually suggested a I guess this is not just about configuration, or data, so maybe we could call it "backpack", i.e. |
I won't hold it against you.
…On Wed, 18 Jan 2017, 09:37 Luke Sampson ***@***.***> wrote:
Looking way back at #126 <#126>
and an aborted attempt at a similar thing, it looks like MariaDB, Vagrant,
Nginx and Apache suffer from similar problems and would benefit.
@deevus <https://github.com/deevus> actually suggested a scoop/data/app
directory which looks very similar to the new plan. (Sorry I dismissed that
idea, dude).
I guess this is not just about configuration, or data, so maybe we could
call it "backpack", i.e. ~/scoop/backpack/[app] since it's just the
things you take with you when go to a new version. Too cheesy?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1220 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA0QghV5F2HnamWa8M9B4EYPBBiig7byks5rTULHgaJpZM4Lk0Qa>
.
|
Yes, that's ok I was right now reading that up and looking at your |
The UNIX way would be separate directories for config But the |
I just really have time to try out, the Thanks all |
I think it would be a nice default though if packages like Node.js would install their own packages into a special directory. 👍 |
Dear @lukesampson
Thanks for this really awesome tool, it really ease my daily workflow a lot
Because right now using
npm -g install ...
will install the packages into the versioning directory of nodejs, therefore when upgrading nodejs, we have to reinstall the packages, it's not so bad right now but would be much better not to re-install anything after upgradingCheers
The text was updated successfully, but these errors were encountered: