You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/config-dependencies.md
+9-12Lines changed: 9 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,13 +7,13 @@ Config dependencies allow you to share and centralize configuration files, setti
7
7
8
8
Config dependencies help you keep all the hooks, settings, patches, overrides, catalogs, rules in a single place and use them across multiple repositories.
9
9
10
-
If your config dependency is named following the `pnpm-plugin-*` pattern, pnpm will automatically load the `pnpmfile.cjs` from its root.
10
+
If your config dependency is named following the `pnpm-plugin-*`or `@*/pnpm-plugin-*`pattern, pnpm will automatically load the `pnpmfile.cjs` from its root.
11
11
12
12
## How to Add a Config Dependency
13
13
14
14
Config dependencies are defined in your `pnpm-workspace.yaml` and must be installed using an exact version and an integrity checksum.
15
15
16
-
Example:
16
+
For example, running `pnpm add --config my-configs` will add this entry to your `pnpm-workspace.yaml`:
17
17
18
18
```yaml title="pnpm-workspace.yaml"
19
19
configDependencies:
@@ -31,7 +31,7 @@ configDependencies:
31
31
32
32
You can load a list of package names that are allowed to be built, using the [`onlyBuiltDependenciesFile`] setting.
33
33
34
-
Example `allow.json` file inside a config dependency ([@pnpm/trusted-deps]):
34
+
Example `allow.json` file inside a config dependency:
0 commit comments