renovate[bot] on cpy-cli-3.x
chore(deps): update dependency … (compare)
zkochan on master
fix(deps): update fast-deep-equ… chore(deps): update typescript (compare)
zkochan on next
fix(deps): update fast-deep-equ… chore(deps): update typescript (compare)
renovate[bot] on write-file-atomic-3.x
zkochan on master
chore(deps): update dependency … (compare)
zkochan on 1918
zkochan on master
feat: add|update [-r] --workspa… (compare)
zkochan on 1918
test: pnpm -r up --workspace (compare)
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.
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.)
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.
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.)
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.
moment-duration-format
and its unadvertised dependency on moment
, but I’m trying the tools Webpack provides to handle special cases.
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.
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?
pnpm test
in the root of the repo