Anton Stoychev

But @hivaga you are right that the documentation is saying the opposite. So @KSXGitHub , @zkochan does that mean the documentation needs updating? Because from the documentation `project` and `package`...

@zkochan @KSXGitHub would ever consider this? It could be under a flag/config that enables it?

Thank you about thinking on this 🙂 1. At the company I'm at right now, we are already using `pnpm.executionEnv.nodeVersion`. I'm assuming this will be replacing this setting? 2. Are...

👋 Hey there, first let me say that I love this RFC and the fact that `pnpm` can unlock workspaces that have multiple runtimes like a package intended for `node`...

PS: Our implementation is a bit different from the examples I've given above regarding CLI commands since we have a similar case but not exactly that one: we execute `eslint`...

@zkochan I'm not sure I fully understand the comment. It's referring to `Package Distributions` but that's not a thing yet and for sure it will never be a thing for...

@zkochan ok but what does that mean for all existing packages and their older versions that will not just disappear? I thought the whole idea of making isolated packages have...

Our team is hitting this issue when using `.pnpmfile.cjs` to remove a `peerDependency` and its `peerDependenciesMeta` info. Locally `pnpm --no-optional --frozen-lockfile --prefer-offline` works. On CI it fails with: ```  ERR_PNPM_LOCKFILE_CONFIG_MISMATCH ...

Wow. I found this issue while I was designing a plugin today and I should say that the fact it was opened less than 2 months ago kinda makes me...

I also hit this and required me to add `actions: write` permission to the job that used `benc-uk/workflow-dispatch`. No need to change repo settings or other job settings.