@effected/pnpm-plugin-effect 0.6.11 → 0.6.12
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +17 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -38,13 +38,29 @@ pnpm add --config @effected/pnpm-plugin-effect
|
|
|
38
38
|
|
|
39
39
|
Requires pnpm 11 or newer, and Node.js >=24.11.0. There is no npm or yarn equivalent: config dependencies and catalogs are pnpm features.
|
|
40
40
|
|
|
41
|
-
The command writes the package into your `pnpm-workspace.yaml
|
|
41
|
+
The command writes the package into your `pnpm-workspace.yaml`:
|
|
42
42
|
|
|
43
43
|
```yaml
|
|
44
44
|
configDependencies:
|
|
45
45
|
"@effected/pnpm-plugin-effect": <version>+sha512-...
|
|
46
46
|
```
|
|
47
47
|
|
|
48
|
+
**Check that file afterwards, and expect to fix it by hand.** On pnpm 11.24.0 `pnpm add --config` writes the new entry **without** an integrity hash, and strips the `+sha512-…` suffix from every *other* config dependency already listed — including ones the command had no reason to touch. A later `pnpm install` does not restore them. Config dependencies are installed ahead of everything else and can contribute hooks that run during install, so the integrity pin is the thing standing between you and an unverified package with that reach.
|
|
49
|
+
|
|
50
|
+
Hand-written hashes are accepted and preserved, so the fix is to put them back:
|
|
51
|
+
|
|
52
|
+
```yaml
|
|
53
|
+
configDependencies:
|
|
54
|
+
"@effected/pnpm-plugin-effect": 0.6.11+sha512-...
|
|
55
|
+
"@your-org/other-config-dep": 1.2.3+sha512-... # restore this one too
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
You can read the correct hash for a version out of the registry:
|
|
59
|
+
|
|
60
|
+
```bash
|
|
61
|
+
npm view "@effected/pnpm-plugin-effect@<version>" dist.integrity
|
|
62
|
+
```
|
|
63
|
+
|
|
48
64
|
## Usage
|
|
49
65
|
|
|
50
66
|
Once installed, all four catalogs are available to every package in the workspace. Reference them from `package.json` by name, in place of a version range. Which field they go in depends on whether you are building an application or a library.
|