Borek Bernard

> I'm not sold about this named workspace set idea, because I would prefer Yarn to deduce which workspaces are needed based on the main ones you want. It's too...

> If one has a large monorepo where CI jobs are started depending on whether a certain "package" changed, having a shared lockfile makes that a bit hard for the...

@acao Just tried and the extension is still causing high CPU of the "Electron" process: This _only_ happens when I enable the GraphQL extension.

Yes, we've got `.graphqlrc.yml` that looks like this: ```yaml projects: shops-manager-tests: schema: - ./sp/apps/shops-manager/src/schema.graphql - scalar Upload documents: ./sp/apps/shops-manager/tests/**/*.ts shops-manager-client: schema: - ./sp/apps/shops-manager/src/schema.graphql - scalar Upload documents: ./sp/libs/shops-manager-client/**/*.ts preview-deployments-autoscaler: schema:...

@acao awesome to hear!

@egonzalez-T Did you find out?

@belaczek Většinou se "cachuje cache" neboli (globální) Yarn cache. Dělá to tak i actions/cache, viz [zde](https://github.com/actions/cache/blob/main/examples.md#node---yarn-2).

M1 doesn't support DDC, this is how Lunar handles it: https://lunar.fyi/#m1 (TL;DR: either gamma tables which is not great or a _very_ involved but clever Raspberry Pi workaround 😄).

Same issue on macOS, will try to regenerate an M1 build by following https://github.com/bartosz-antosik/vscode-spellright/pull/503 and some info from https://github.com/bartosz-antosik/vscode-spellright/issues/502.

~~One annoying thing is that each update breaks this – I had everything working for v3.0.60 and now have to re-do it for v3.0.62 (initially, I didn't even notice that...