Zoltan Kochan
Zoltan Kochan
>  ERR_PNPM_LOCKFILE_CONFIG_MISMATCH  Cannot proceed with the frozen installation. The current "pnpmfileChecksum" configuration doesn't match the value found in the lockfile Update the lockfile.
> Same issue, AWS app runner is broken from yesterday Error:  ERR_PNPM_BAD_PM_VERSION  This project is configured to use v8.10.4 of pnpm. Your current pnpm is v9.0.1 It is not broken....
So either use that version of pnpm or change the field to the version that you want to run. There's no issue on pnpm's end.
@AntonOfTheWoods in the past we had a problem, users modified the `.pnpmfile.cjs` file but the lockfile was not updated. We have added the checksum of the pnpmfile to the lockfile....
Could you just make a workspace from it? Then it will work as you'd expect.
Yes, correct at the moment. Alex ezt Ãrta (idÅ‘pont: 2021. jan. 9., Szo 14:22): > So if I want to have any file: dependency (so that pnpm would effect it's...
I don't know, it might be useful to at least print an info message in this case.
Correct, this is how it currently works. It will not install dependencies in external projects.
You can try to use it with the [dependenciesMeta.injected](https://pnpm.io/package_json#dependenciesmetainjected). It will hard link the external package as a regular dependency and install its dependencies.
@farfromrefug it works the way you want it to work in pnpm v7