@activeledger/nano-gateway 4.10.1 → 5.0.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 +1 -1
  2. package/package.json +6 -6
package/README.md CHANGED
@@ -6,7 +6,7 @@ A lightweight, permissioned SSE + read gateway for [nano](https://github.com/act
6
6
 
7
7
  ## Why this exists
8
8
 
9
- Activecore (`@activeledger/activecore`, `packages/core`) is nano's originally-planned data source, but it isn't running on the devnet this was built against, and its SSE controller (`controllers/sse.ts`) is written against Node's raw `http.IncomingMessage`/`ServerResponse` API - `res.setHeader()`, `res.write()`, `res.flushHeaders()`, `req.socket.setTimeout()`. The `@activeledger/httpd` this repo actually ships today is built on `uWebSockets.js` (confirmed by reading its published `lib/httpd.js`, not assumed) - route handlers get a raw uWS `HttpResponse`, which has none of those methods. Activecore's SSE path would throw immediately if invoked against it. That's very likely a real, standing cause of Activecore's unreliability, independent of anything else.
9
+ Activecore (`@activeledger/activecore`, formerly `packages/core`, removed in 5.0.0) was nano's originally-planned data source, but it wasn't running on the devnet this was built against, and its SSE controller (`controllers/sse.ts`) is written against Node's raw `http.IncomingMessage`/`ServerResponse` API - `res.setHeader()`, `res.write()`, `res.flushHeaders()`, `req.socket.setTimeout()`. The `@activeledger/httpd` this repo actually ships today is built on `uWebSockets.js` (confirmed by reading its published `lib/httpd.js`, not assumed) - route handlers get a raw uWS `HttpResponse`, which has none of those methods. Activecore's SSE path would throw immediately if invoked against it. That's very likely a real, standing cause of Activecore's unreliability, independent of anything else.
10
10
 
11
11
  This package is a much smaller, purpose-built replacement for just what nano needs: a permissioned SSE subscribe endpoint, and the handful of reads nano's mini-SPI needs. It's modeled directly on `packages/hybrid` - direct database access via `ActiveDSConnect`, no consensus involvement, runs as a companion process alongside a real node.
12
12
 
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@activeledger/nano-gateway",
3
3
  "description": "Lightweight, permissioned SSE + read gateway for nano light-node clients - runs alongside a real Activeledger node, direct DB access like activehybrid, no Activecore dependency.",
4
- "version": "4.10.1",
4
+ "version": "5.0.1",
5
5
  "engines": {
6
6
  "node": ">=24.0.0"
7
7
  },
@@ -51,11 +51,11 @@
51
51
  "jsnext:main": "./es/index.js",
52
52
  "module": "./es/index.js",
53
53
  "dependencies": {
54
- "@activeledger/activecrypto": "4.10.1",
55
- "@activeledger/activedefinitions": "4.10.1",
56
- "@activeledger/activelogger": "4.10.1",
57
- "@activeledger/activeoptions": "4.10.1",
58
- "@activeledger/httpd": "4.10.1",
54
+ "@activeledger/activecrypto": "5.0.1",
55
+ "@activeledger/activedefinitions": "5.0.1",
56
+ "@activeledger/activelogger": "5.0.1",
57
+ "@activeledger/activeoptions": "5.0.1",
58
+ "@activeledger/httpd": "5.0.1",
59
59
  "typescript": "7.0.2"
60
60
  }
61
61
  }