Usage Error: This project is configured to use yarn about corepack

[arcanis]

That's the expected behaviour. See the documentation:

COREPACK_ENABLE_STRICT can be set to 0 to prevent Corepack from throwing error if the package manager does not correspond to the one defined for the current project. This means that if a user is using the package manager specified in the current project, it will use the version specified by the project's packageManager field. But if the user is using other package manager different from the one specified for the current project, it will use the system-wide package manager version.

You can also explicitly call corepack yarn ... on pnpm projects (or corepack pnpm ... on Yarn projects) to bypass this check.

[cdtut]

Even with no COREPACK_ENABLE_STRICT the error should not happen if pnpm --dir or yarn --cwd point to location outside current project.

[arcanis]

Corepack has no knowledge of what the underlying package manager CLIs look like, and can only make trivial assumptions about it. If you want a similar behaviour, you'll need to cd into the target directory and run the command from there.

[cdtut]

can only make trivial assumptions about it

Can be trivial if --dir is on pnpm or --cwd is on yarn then skip warning.