🔧 Repository: Add root backstage yarn plugin any workspace can opt into via `bcp.json`

[kurtaking]

📜 Description

The Backstage yarn plugin makes it incredibly simple to manage upgrades, but each workspace must install the plugin. I'm wondering if it would be possible to install a root level version of the plugin and then use bcp.json to let workspaces opt in to using this feature.

It's worth noting I have no idea if a feature like this is possible or not 🤔.

Proposal

The repository installs a single version of the yarn plugin that all workspaces leverage.

Directory structure:

.yarn/
└── plugins/
    └── @yarnpkg/
        └── plugin-backstage.cjs
.yarnrc.yml
workspaces/
├── workspace-a/
│   ├── .yarnrc.yml
│   └── package.json
└── workspace-b/
    ├── .yarnrc.yml
    └── package.json

Could we simply point the path to the root directory?

plugins:
  - checksum: b3b00465cee9a55ea92b7555876084a6dbfb4b9dd2ce7617a0bca1c138dec6b33befabdff7f4035b2a2ad70d59a05dad3a8faf3a34d3bec21fa7949a497fdf48
-    path: .yarn/plugins/@yarnpkg/plugin-backstage.cjs
+    path: ../.yarn/plugins/@yarnpkg/plugin-backstage.cjs
    spec: 'https://versions.backstage.io/v1/releases/1.47.2/yarn-plugin'

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

Are you willing to submit PR?

Yes I am willing to submit a PR!

[awanlin]

Hi @kurtaking, I think your Current and Proposal need to be flipped ;)

Can you bring this up at the next Community Plugins SIG?