Is it possible to have lock files in each workspace pacckage?

[aspirisen]

Hello, i wonder if it is possible to have lock files in each workspace, but do not install the dependencies like it is separate package? So when i add dependency in workspace package pnpm updates package.json in the package, update its lock file, but pnpm will install the dependency like i would run "pnpm instal" in the root.

The use case:
I have dozens of packages and each of them have its own github repo. I want to create "super" repo where i would attach all other repos as git submodules. In the "super" repo i define workspace with paths to these submodules. The issue is that "super" repo is only for development purpose, i.e. it is not supposed to have its own lock file. At the same time all the packages do no know that they can be a part of workspace and leave independently. So when i push smth in workspace package repo CI should install its dependencies from its lock file.
Thank.

[zkochan]

You can try to set the shared-workspace-lockfile setting to false. But it will also create separate node_modules for every project. So installation will be a lot slower.

Maybe you can generate your own lockfile using this library: https://github.com/pnpm/pnpm/tree/main/packages/make-dedicated-lockfile

[aspirisen]

@zkochan thanks, If i would set shared-workspace-lockfile and it will create separate node_modules, does mean that i could have i.e. two React in bundle, or the symlink will still point to the same location?

[zkochan]

No, the symlink will not point to the same location.

[linhuiw]

I think this is the newest link for shared-workspace-lockfile

[levrik]

@zkochan Would it be possible to have only a single package in the workspace with its own lockfile? I'm having a workspace with a legacy app using React 17 and multiple newer packages using React 18. Except for the legacy application, everything gets built through a single Webpack. To avoid multiple copies of React to be included in the build, I need these to symlink to the same location. But at the same time I cannot enable shared-workspace-lockfile due to #7158 as transitive dependencies define "@types/react": "*" in their deps and then resolve to ^18.0.0 also for the single app which depends on "@types/react": "^17.0.0". This can be solved by adding @types/react as peer deps to these packages through pnpm.packageExtensions but they are a lot! I can also solve it by overriding the resolution through tsconfig.json but TBH I'm afraid that there are more similar cases that result in subtle bugs and aren't as noticable as a failing build in this case.

For me the perfect solution would be to have a separate lockfile for that one app and a shared for the rest. Please note that the app using a separate lockfile would still need to be able to access other packages from the workspace which are shared between the legacy and new app so simply excluding that one package from the PNPM workspace also doesn't work.

Edit: pnpm doesn't even respects excluded packages when executing pnpm install inside subdirectories. It simply installs the workspace root instead of the nested excluded package.