option to for .store location about pnpm

[rstacruz]

i got better use cases for you:

1. keep the store in ~/.pnpm/node-4/store/ so that Babel doesn't take up 100MB for every project I have
2. since the 'global' store is prepended by the node major version, I can switch node versions and switch my compiled modules out by symlinks

this is actually the very reason I put pnpm together! I'm still contemplating on how to best do this, whether it's to symlink ~/.pnpm/node-4/store/[email protected] -> ~/project/node_modules/.store/[email protected] -> ~/project/node_modules/lodash, or to skip the 2nd symlink entirely. Both have their pros and cons and I'm waiting to use pnpm for a while to get a feel of which would be the better approach. 👍

[gtramontina]

Ooh! I like where this is going! 🍻

[jkroso]

@rstacruz what's the potential benefit of the extra symlink?

PS: the symlink approach is great in general since It saves tons of rm -rf node_modules && npm i though you will run into problems with babel and plugin-ish modules since people rely on the implementation details of npm occasionally. So expect to do a bit of hackery.

[rstacruz]

jkroso: easier to account for what packages may (or may not) be in use. what if you stop using a dependency in one of your projects... how do we keep track that no project needs it anymore?

[rstacruz]

okay there's a super secret flag that lets you do this:

npm config set pnpm_store_path node_modules/.store  # <- default

not documenting it though, it's easy to screw this up if you don't know what you're doing

[kevinverelst]

Setting this flag does not seem to work for me, the packages are still stored in node_modules/.store.
Ideas are welcome

[kevinverelst]

Nvm, the flag is renamed to store_path it seems

[zkochan]

hey, I documented the usage of a shared store: https://github.com/rstacruz/pnpm/blob/master/docs/recipes/shared-store.md

[kevinverelst]

Great! Thanks

[dandv]

The link to the pnpm shared store is now dead. Pointing to that other issue for SEO.