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
A globallink install strategy should be included and would work similar to how the linked strategy works now. However, instead of the packages being saved in ./node_modules/.store, they would be saved in /path/to/npm/global/node_modules/.store.
This will allow developers to reduce the amount of package duplication across projects.
This will also create an update to the clean-install command where the packages (and exact dependencies) for a project are deleted from the global store and re-installed.
The text was updated successfully, but these errors were encountered:
@TheBrenny Thanks for taking the time to share your idea! New ideas are always appreciated and are better suited for our RFC repo instead since that's the right place in order to get more attention from the rest of the team and the community.
A
globallink
install strategy should be included and would work similar to how thelinked
strategy works now. However, instead of the packages being saved in./node_modules/.store
, they would be saved in/path/to/npm/global/node_modules/.store
.This will allow developers to reduce the amount of package duplication across projects.
This will also create an update to the
clean-install
command where the packages (and exact dependencies) for a project are deleted from the global store and re-installed.The text was updated successfully, but these errors were encountered: