@homeflare/alchemy 0.3.1 → 0.3.2

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 +5 -6
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -3,7 +3,7 @@
3
3
  Custom [Alchemy](https://alchemy.run) providers for gaps the vendor SDK leaves.
4
4
 
5
5
  ```sh
6
- bun add @homeflare/alchemy alchemy@2.0.0-beta.78 effect@4.0.0-rc.115 \
6
+ bun add @homeflare/alchemy alchemy@2.0.0-beta.79 effect@4.0.0-rc.115 \
7
7
  @effect/platform-node@4.0.0-rc.115 cloudflare@4.5.0 mime@4.1.0
8
8
  ```
9
9
 
@@ -76,7 +76,7 @@ like a bad credential.
76
76
  ## Peers — and one override you need
77
77
 
78
78
  ```sh
79
- bun add @homeflare/alchemy alchemy@2.0.0-beta.78 effect@4.0.0-rc.115 \
79
+ bun add @homeflare/alchemy alchemy@2.0.0-beta.79 effect@4.0.0-rc.115 \
80
80
  @effect/platform-node@4.0.0-rc.115 cloudflare@4.5.0 mime@4.1.0
81
81
  ```
82
82
 
@@ -116,10 +116,9 @@ stay there. The override is still the only thing that holds the set together.
116
116
  `Cloudflare/Workers/WorkerBridge → @effect/platform-node/NodeServices` even when you only
117
117
  import the Proxmox subpath.
118
118
 
119
- ⚠️ So is `mime`. Alchemy 78's `@alchemy.run/cloudflare-runtime` imports it and does
120
- not declare it. `@effect/platform-node` has `mime` as its own dependency, but a clean
121
- consumer install (no hoist) cannot see that copy — measured 2026-09-17, every subpath
122
- threw `Cannot find package 'mime'` until it was installed next to the peers.
119
+ ⚠️ So is `mime`. Alchemy 78's `@alchemy.run/cloudflare-runtime` imported it without
120
+ declaring it (measured 2026-09-17). 79 declares it; the peer stays so a consumer
121
+ that followed the 78 README does not drop a required line.
123
122
 
124
123
  ⚠️ So is `cloudflare`. It was marked optional in 0.1.1, which claimed the `/cloudflare`
125
124
  subpath would degrade without it — measured 2026-09-16, the subpath does not load at all:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@homeflare/alchemy",
3
- "version": "0.3.1",
3
+ "version": "0.3.2",
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",
@@ -51,7 +51,7 @@
51
51
  },
52
52
  "peerDependencies": {
53
53
  "@effect/platform-node": "4.0.0-rc.115",
54
- "alchemy": "2.0.0-beta.78",
54
+ "alchemy": "2.0.0-beta.79",
55
55
  "cloudflare": ">=4.5.0",
56
56
  "effect": "4.0.0-rc.115",
57
57
  "mime": "4.1.0"