v11: How to use configDependencies to define common configuration items?

[pro-sumer]

In v10 I had several configuration items (such as lockfile and allowedDeprecatedVersions) in my global pnpm configuration file. Apparently v11 no longer allows/supports this. Instead there's the concept of configDependencies now, but I don't understand its documentation and can't find any examples on the web.

How/where must I define my-configs (from the example in the documentation)?

How can I use the mentioned attributes in my-configs?

Can somebody give a full example?

[pro-sumer]

This might help?

https://gitnation.com/contents/configurational-dependencies-in-pnpm

(Plan to watch it later today)

[zkochan]

Here is an example of a config dependency that update settings: https://github.com/pnpm/plugin-better-defaults

[Om-singh-ui]

configDependencies in v11 are just shareable config packages.

Create my-configs/package.json:

{
  "name": "my-configs",
  "version": "1.0.0",
  "pnpm": {
    "lockfile": true,
    "allowedDeprecatedVersions": {
      "left-pad": "*"
    }
  }
}

In your main project’s package.json, add:

{
  "pnpm": {
    "configDependencies": ["my-configs"]
  }
}

For a local config package, use the file: protocol:

{
  "pnpm": {
    "configDependencies": ["file:../path/to/my-configs"]
  }
}

TL;DR: Put shared config in a package and reference it via configDependencies.

[zkochan]

No, this is incorrect. The settings can only be updated via the updateConfig hook: https://pnpm.io/11.x/pnpmfile#hooksupdateconfigconfig-config--promiseconfig

[pro-sumer]

How can I do this using a local package (in another Git repo) that defines my settings, without publishing it to a registry?