[Bug] `--cwd` gets ignored when specified inside package.json script

• I’d be willing to implement a fix

Describe the bug

{
  "scripts": {
    "foo": "yarn --cwd .yarn exec cd"
  }
}

Running yarn foo prints out the current path, not .yarn as specified in --cwd.

Running yarn --cwd .yarn exec cd directly in the shell produces the correct output.

To Reproduce

Use the following package.json

{
  "name": "foo",
  "version": "1.0.0",
  "license": "MIT",
  "scripts": {
    "foo": "yarn --cwd .yarn exec cd"
  }
}

Run yarn foo from the package directorty.

Environment if relevant

• OS: Windows 10 v2004
• Node version: 12.13.1
• Yarn version: 2.4.0

[merceyz]

This is a valid issue, you’re running into https://github.com/yarnpkg/berry/pull/1812#discussion_r485873759, as a workaround you can specify the path as the first argument

yarn ../another/package exec pwd

[Mithras]

I don’t think --cwd is doing anything at all (inside or outside of package.json). It can be confirmed with a simple yarn --cwd /expected exec pwd. Output would be anything but /expected. What exactly --cwd is supposed to be doing?