You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: