hazo_connect 3.10.0 → 3.10.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/CHANGE_LOG.md +15 -0
  2. package/package.json +6 -14
package/CHANGE_LOG.md CHANGED
@@ -5,6 +5,21 @@ All notable changes to this project will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## 3.10.1 — 2026-08-04
9
+
10
+ ### Changed
11
+
12
+ Removed peer declarations that made the hazo_* peer graph cyclic. npm's
13
+ dependency solver backtracks through peer cycles until it exhausts the V8 heap:
14
+ a consumer installing this package without `legacy-peer-deps` would see
15
+ `npm install` die with "JavaScript heap out of memory" rather than any
16
+ actionable error. With the ecosystem acyclic, a strict install of the full set
17
+ now resolves normally.
18
+
19
+ - Dropped the `hazo_debug` and `hazo_logs` peers — neither is imported
20
+ anywhere in `dist/`.
21
+
22
+
8
23
  ## 3.10.0 (2026-07-31)
9
24
  - fix: `SqliteAdapter.claimRows()` / `BetterSqlite3Adapter.claimRows()` now open their transaction with `BEGIN IMMEDIATE` instead of a plain (DEFERRED) `BEGIN`. `types.ts` already documented "BEGIN IMMEDIATE" for claimRows, but both adapters issued a plain `BEGIN`. On `BetterSqlite3Adapter` this was a real correctness bug: `claimRows` is the lease primitive that decides which process gets to run a scheduled job, and a DEFERRED transaction lets two OS processes on one WAL database both take a read lock, so the second process's `UPDATE` can fail with `SQLITE_BUSY_SNAPSHOT` — which `busy_timeout` does not retry, because the snapshot is already stale. `BEGIN IMMEDIATE` makes the second process block on the write lock for up to `busy_timeout` and then correctly observe the first process's claim. The in-process `_claimQueue` promise chain only ever serialized calls within one Node process and did nothing across processes — that gap is unchanged, but the cross-process case is now handled by the write lock instead. `SqliteAdapter` (sql.js) is single-process/in-memory and gets no equivalent safety benefit from this — see below.
10
25
  - feat: `transaction(fn, { immediate?: boolean })` — both SQLite adapters accept an optional second argument. `immediate: true` opens with `BEGIN IMMEDIATE`; omitting it keeps the existing plain `BEGIN`, so existing callers are unaffected. `claimRows()` on both adapters now calls `transaction(fn, { immediate: true })` internally.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "hazo_connect",
3
- "version": "3.10.0",
3
+ "version": "3.10.1",
4
4
  "description": "Module to connect to the data store (postgres via postgrest, supabase, etc)",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -101,8 +101,6 @@
101
101
  "peerDependencies": {
102
102
  "hazo_config": "^2.4.1",
103
103
  "hazo_core": "^1.3.0",
104
- "hazo_debug": "^3.1.1",
105
- "hazo_logs": "^2.1.1",
106
104
  "hazo_ui": "^6.3.1",
107
105
  "lucide-react": "^0.553.0",
108
106
  "next": "^14.0.0 || ^16.0.0",
@@ -118,9 +116,6 @@
118
116
  "hazo_config": {
119
117
  "optional": true
120
118
  },
121
- "hazo_debug": {
122
- "optional": true
123
- },
124
119
  "hazo_ui": {
125
120
  "optional": true
126
121
  },
@@ -139,9 +134,6 @@
139
134
  "sonner": {
140
135
  "optional": true
141
136
  },
142
- "hazo_logs": {
143
- "optional": false
144
- },
145
137
  "zod": {
146
138
  "optional": true
147
139
  }
@@ -163,13 +155,13 @@
163
155
  "@types/sql.js": "^1.4.9",
164
156
  "eslint": "^8.57.0",
165
157
  "eslint-config-next": "14.2.33",
166
- "hazo_config": "^2.4.1",
167
- "hazo_core": "^1.3.0",
168
- "hazo_debug": "^3.1.1",
169
- "hazo_logs": "^2.1.1",
158
+ "hazo_config": "^2.4.2",
159
+ "hazo_core": "^1.3.1",
160
+ "hazo_debug": "^3.2.0",
161
+ "hazo_logs": "^2.2.0",
170
162
  "ioredis": "^5.3.2",
171
163
  "neo4j-driver": "^5.14.0",
172
- "hazo_ui": "^6.3.1",
164
+ "hazo_ui": "^6.8.0",
173
165
  "jest": "^30.2.0",
174
166
  "jest-environment-node": "^30.2.0",
175
167
  "lucide-react": "^0.553.0",