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
Hello I hope you are well! One question... Do you have in mind a virtual store shared by projects?
Something like a store in which absolutely all dependencies are stored and symbolic links to it are created in each project. This (although I know it's not easy) would save much more space.
To give an example, suppose the virtual store is in ~/.virtual-store and we have a project (project A) in which we execute "pnpm add -ED eslint", this could save the dependencies in the virtual store and create a symbolic link from the virtual store to the project where it is needed.
But being shared, we could create a new project (project B) and in doing something like "pnpm add -ED --virtual-store (or --offline) eslint" and this, like project A, would create a link symbolic to the virtual store. Thus maintaining a single "disk space" since we would not have 20Mb in project A and B, but those 20Mb would only be in the virtual store.
At the moment, I achieved a similar effect, the only problem I have for now is that if we already have (for example) eslint in the virtual store and I go to another project in which eslint is not used and install (for example) nodemon, this adds me nodemon to the virtual store, but removes eslint.
Although... If I go back to the first project that uses eslint and do a "pnpm fetch" it re-adds eslint to the virtual store WITHOUT "removing" nodemon. So the result ends up being: eslint + nodemon in a virtual store, which is the only one that takes up disk space, while my two projects only symbolically link to that store.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello I hope you are well! One question... Do you have in mind a virtual store shared by projects?
Something like a store in which absolutely all dependencies are stored and symbolic links to it are created in each project. This (although I know it's not easy) would save much more space.
To give an example, suppose the virtual store is in ~/.virtual-store and we have a project (project A) in which we execute "pnpm add -ED eslint", this could save the dependencies in the virtual store and create a symbolic link from the virtual store to the project where it is needed.
But being shared, we could create a new project (project B) and in doing something like "pnpm add -ED --virtual-store (or --offline) eslint" and this, like project A, would create a link symbolic to the virtual store. Thus maintaining a single "disk space" since we would not have 20Mb in project A and B, but those 20Mb would only be in the virtual store.
At the moment, I achieved a similar effect, the only problem I have for now is that if we already have (for example) eslint in the virtual store and I go to another project in which eslint is not used and install (for example) nodemon, this adds me nodemon to the virtual store, but removes eslint.
Although... If I go back to the first project that uses eslint and do a "pnpm fetch" it re-adds eslint to the virtual store WITHOUT "removing" nodemon. So the result ends up being: eslint + nodemon in a virtual store, which is the only one that takes up disk space, while my two projects only symbolically link to that store.
Beta Was this translation helpful? Give feedback.
All reactions