Multiple lock files for fine-grained installs

[mcmxcdev]

We recently switched from yarn v1 to yarn berry, and were unable to replicate a certain behavior of yarn v1:

Before the migration, we had this config:

  "workspaces": {
    "packages": [
      "packages/!(dashboard-e2e)"
    ]
  },

This made sure that our e2e subpackage was not part of the workspace, so that the e2e run in the CI only had to install e.g. Cypress and not the whole monorepo tree. Additionally, we didn't want that deployments of individual packages would need to download and install Cypress, which wouldn't be used except for e2e tests.

With the config above, we had a yarn.lock in the root and a separate one for dashboard-e2e.

The config above doesn't seem to work anymore. How can we go back to the yarn v1 behavior to save precious CI build minutes and avoid wasting resources?