-
Hello, I'm coming from #2198 where is was recommended to create a discussion :) I read the case, and I'm not sure I found the solution to my issue, so I'm asking here, sorry if the solution was already mentioned, then I misunderstood it. What I want to do: I want to package one of my package in a tarball (like https://pnpm.io/cli/pack) but also containing all the dependencies. The goal is to have something I can untar on a server and run, without pnpm installed or a populated store directory. With npm, it was easy, I just tarred both the build files and the node_modules together and it was all good. With pnpm phantom dependency protection (symlinks), it's not very easy to do. I want to avoid shipping the whole pnpm-store as it might contain useless packages from other project/build. Am I missing something? Would there be value, for example, in adding an option I saw the suggestion of
Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 18 replies
-
It does not directly answer your question, but have you tried using the pnp linker? I think the Yarn maintainers designed that installation strategy exactly for the case where you want to copy the dependency files to production. From reading the docs, it looks like the |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
same question |
Beta Was this translation helpful? Give feedback.
pnpm deploy
is the new way to do this - #4378 (comment)