Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

npm should use Local AppData not Roaming AppData for globally installed modules #15675

Closed
Daniel15 opened this issue Feb 5, 2017 · 1 comment

Comments

@Daniel15
Copy link

Daniel15 commented Feb 5, 2017

Windows has two different types of AppData directories:

  • %APPDATA% (eg. C:\Users\Daniel\AppData\Roaming\) - Contains user settings. In a corporate/domain environment, this can be configured to be synchronised across computers, so it should generally only hold things you'd actually need to keep in sync. Settings/config is a good example.
  • %LOCALAPPDATA% (eg. C:\Users\Daniel\AppData\Local\) - Contains other random junk. It's like AppData except for stuff that wouldn't need to be kept in sync across machines. Per-user temporary files and local caches fall into this category.

npm places globally installed modules in the roaming directory, but it should really use the local one.

@Daniel15 Daniel15 changed the title npm should use Local AppData, not Roaming AppData npm should use Local AppData not Roaming AppData for globally installed modules Feb 5, 2017
@kenany
Copy link
Contributor

kenany commented Feb 5, 2017

See #4564

@kenany kenany closed this as completed Feb 5, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants