injected workspace packages without shared lock file

[y-nk]

Hello,

I'm trying to experiment a new setup for a monorepo which consists of services (docker images) and packages (npm packages).

- packages/
  - package-1
  - package-2
- services/
  - service-1
  - service-2

What i want to achieve is having those packages referenced by their workspace packages, but since i'm building docker images i would like to avoid the mess of having a shared lock file, so that i can "just" copy the node_modules into my docker container. for that, the pnpm config i'm rooting for is:

node-linker = isolated
shared-workspace-lockfile = false

with that config, i found that workspace packages are symlinked and therefore cannot be copied over when building the image, so i tried turning them into hardlinks.

inject-workspace-packages = true

i think it's a bug, because adding this will create a monorepo-root/.node_modules with the hardlinks, and each service would have symlinks of the workspace packages to there, rather than hardlinks in each services directly, but i could go on with removing it and using dependenciesMeta[].injected as an alternative. when doing so, the workspace packages are properly hardlinked, but the dependencies of the packages are here too, but the level under (deps of deps) is not linked properly. I can see them in the node_modules but once running the bin of a service, it breaks at this level.

is that a bug? or am i missing something here?