@homeflare/alchemy 0.1.0 → 0.1.1

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.
Files changed (2) hide show
  1. package/README.md +35 -2
  2. package/package.json +9 -3
package/README.md CHANGED
@@ -50,13 +50,46 @@ API Key. An empty value fails closed with a message saying so, because an empty
50
50
  a denied grant rather than a missing file, and `Bearer ` + nothing 401s in a way that reads
51
51
  like a bad credential.
52
52
 
53
- ## Peers
53
+ ## Peers — and one override you need
54
54
 
55
- `alchemy` >= 2.0.0-beta.77 · `cloudflare` >= 4.5.0 · `effect` >= 4.0.0-rc.112
55
+ ```sh
56
+ bun add @homeflare/alchemy alchemy@2.0.0-beta.77 effect@4.0.0-rc.112 \
57
+ @effect/platform-node@4.0.0-rc.112
58
+ ```
56
59
 
57
60
  ⚠️ Peers, not dependencies: Alchemy's resource registry and Effect's context both break if
58
61
  two copies load in one process.
59
62
 
63
+ ⛔ **Add this to your `package.json`, or the install works and the import throws:**
64
+
65
+ ```json
66
+ {
67
+ "overrides": {
68
+ "effect": "4.0.0-rc.112",
69
+ "@effect/platform-node": "4.0.0-rc.112",
70
+ "@effect/platform-node-shared": "4.0.0-rc.112",
71
+ "@effect/platform-bun": "4.0.0-rc.112"
72
+ }
73
+ }
74
+ ```
75
+
76
+ 🔴 **Why, measured 2026-09-16 against a clean consumer install of 0.1.0.** Effect's `rc`
77
+ line is not semver-compatible with itself, and two separate skews bite:
78
+
79
+ | what resolves | what happens |
80
+ | ---------------------------------------------------------------- | ------------------------------------------------------ |
81
+ | `effect` → rc.115 | `TypeError: Config.string is not a function` at import |
82
+ | `@effect/platform-node-shared` → rc.115 while `effect` is rc.112 | `Cannot find module 'effect/ByteSize'` |
83
+
84
+ The second is the nastier one: `@effect/platform-bun@rc.112` depends on
85
+ `platform-node-shared` at `^4.0.0-rc.112`, which resolves _up_ to rc.115 — whose own peer
86
+ is `effect@^4.0.0-rc.115`. Nothing fails at install time. An override is the only thing
87
+ that holds the set together.
88
+
89
+ ⚠️ `@effect/platform-node` is **required, not optional**: Alchemy's module graph reaches
90
+ `Cloudflare/Workers/WorkerBridge → @effect/platform-node/NodeServices` even when you only
91
+ import the Proxmox subpath.
92
+
60
93
  ## License
61
94
 
62
95
  MIT © Timothy Schneider
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@homeflare/alchemy",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "Custom Alchemy providers for Cloudflare, Proxmox, OpenBao, Forgejo and Talos.",
5
5
  "homepage": "https://github.com/taslabs-net/homeflare-kit/tree/main/packages/alchemy#readme",
6
6
  "bugs": "https://github.com/taslabs-net/homeflare-kit/issues",
@@ -50,8 +50,14 @@
50
50
  "access": "public"
51
51
  },
52
52
  "peerDependencies": {
53
- "alchemy": ">=2.0.0-beta.77",
53
+ "@effect/platform-node": "4.0.0-rc.112",
54
+ "alchemy": "2.0.0-beta.77",
54
55
  "cloudflare": ">=4.5.0",
55
- "effect": ">=4.0.0-rc.112"
56
+ "effect": "4.0.0-rc.112"
57
+ },
58
+ "peerDependenciesMeta": {
59
+ "cloudflare": {
60
+ "optional": true
61
+ }
56
62
  }
57
63
  }