@nthypes Ah crud, I was just going to look at Parcel to bundle my code to put in a Docker image.
…which doesn’t seem to be the best idea, as it looks it’s more web-focused… hmm.
To elaborate: I have a multi-stage Dockerfile. In the first stage, I compile my code and then prune development dependencies. In the second stage, I copy over the compiled files and the now-minimal
node_modules. Or at least, that’s how I did it before. I’m not sure how to handle pnpm’s symlinking and workspace dependencies and all that.
And templates to create new packages within the monorepo? Or to manage packages in general—add, delete, rename, manage common files or
package.json settings, and so on. (I realize that may be out of scope for pnpm, so I’m open to any suggestions outside it as well.)
And run the commands with pnpm run on the monorepo root dir.
Re: the multi-stage Dockerfile, I did manage to get a working version by first running
pnpm install -r and then copying only the package I wanted into a different directory using cp -rL, which dereferences symlinks. The problem is, I ended up with a 4.3 GB image, because each package in the repo might have symlinks in its node_modules to another package which might have symlinks yadda yadda, so it’s not a single flat directory, like pnpm creates on its own, but rather a tree with many nested copies of each dependency.
we have a couple utils that get duplicated for each package that uses those
so not only do I get copies of the package but also its node_modules
They’re a godsend in development but it gets complicated when you want to deploy. Maybe
pnpm needs something that will, in a given package directory, dereference the symlinks and flatten the node_modules directory. (Unless a command like that exists already. I haven’t yet been able to find anything.)
Yeah, I don't see anything in the docs like that
@mledom_twitter, I found something that helped me: https://github.com/lerna/lerna/issues/858#issuecomment-487083308
I adapted the Webpack config to my project and used it to compile my code in a
build stage. In the second stage, I only copy over the bundle (modulo some fiddling to get source maps). Now I have a tiny (relatively speaking), functional image.
The only issue I’m having is with
moment-duration-format and its unadvertised dependency on moment, but I’m trying the tools Webpack provides to handle special cases.
@zkochan when using the
shared-workspace-lockfile feature for workspaces the note leads me to believe that my node_modules folders should be empty since all packages are hard linked to the root node_modules. Is that what I should expect? I ask because having the my linked local packages is causing issue when packaging for serverless.
@nthypes you may run
pnpm run cmd --filter foo... but it will include foo as well. Not only its deps
I just cloned the pnpm repository and ran pnpm test -r to get a baseline before trying to implement a feature. packages/config fails:
│ > @pnpm/config@5.0.2 tsc redacted\packages\config
│ > rimraf lib && tsc
│ src/index.ts(1,32): error TS2307: Cannot find module '@pnpm/constants'.
│ src/index.ts(2,23): error TS2307: Cannot find module '@pnpm/error'.Is this temporary breakage because of ongoing development or something to open an issue for?
Hang on, it works when I enter the directory and run it manually.
@Aankhen run
pnpm test in the root of the repo
@mledom_twitter why would you want that? it would give access to all deps from all projects in the monorepo
@zkochan I'm trying to deploy with serverless. We have a mono repo with a bunch of packages for individual lambda functions and then shared packages. Those shared packages are linked. Some of those shared packages depend on others. When I try to build the deploy package its either including multiple copies of node_modules or not including deps modules down the shared package paths. I have yet to find a great way to flatten all depends into a deployable file to remove duplicates and shrink our zip to meaningful sizes.
I've been trying to use the jetpack serverless plugin to include or exclude paths to reduce this deep recursive shared package structure but not having any luck getting a correctly built zip
