[Bug?]: Workspace focus feature does not respect enableScripts config

[adam-thomas-privitar]

Self-service

• I'd be willing to implement a fix

Describe the bug

When using the workspace focus feature, the enableScripts setting is not respected in that if it is false, the postinstall's still seem to be executed. This is the case wether its in .yarnrc or used an env var for example yarn_enable_scripts=false yarn workspaces focus -A --production.

To reproduce

I was unable to use sherlock because I couldnt see how to pass the yarn_enable_scripts=false. Let me know if theres a way.

Basically need a package.json with a echo hello postinstall script. Then execute yarn_enable_scripts=false yarn workspaces focus -A --production and observe hello is echoed.

Environment

System:
    OS: macOS 11.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
  Binaries:
    Node: 14.17.0 - /private/var/folders/t1/kyx57bk12hs04wln8l_5z2m00000gn/T/xfs-44831458/node
    Yarn: 3.2.0 - /private/var/folders/t1/kyx57bk12hs04wln8l_5z2m00000gn/T/xfs-44831458/yarn
    npm: 6.14.13 - ~/.nvm/versions/node/v14.17.0/bin/npm

Additional context

No response

[yarnbot]

Hi! 👋

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolutions). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label. Thanks for helping us triaging our repository! 🌟

[MagnusHJensen]

We are seeming to run into this issue, aswell.
Our setup looks like

install script
with a "postinstall" script that runs @chakra-ui/cli to generate theme-typings.
This is a devDep, so running yarn workspaces focus --production does not include the package, and therefore fails the execution, due to unfound packages.
When in fact having the enableScripts: false in the .yarnrc.yml file
Would be lovely if it actually respected the configuration file.

[JuliusHenke]

I am experiencing the same behaviour both with yarn install and yarn workspaces focus -A --production.
Setting enableScripts=false in .yarnrc.yml or YARN_ENABLE_SCRIPTS=false as an environment variable still triggers the postinstall script.