@nwire/endpoint 0.10.0 → 0.10.1

package/dist/endpoint.d.ts

@@ -28,7 +28,7 @@
  * ## Why this exists
  *
  * Every framework eventually needs a process layer — something that knows
- * about SIGTERM, drains in-flight requests, exposes `/healthz`, and binds
+ * about SIGTERM, drains in-flight requests, exposes `/live`, and binds
  * to a port. Most frameworks bolt this on as a deployment afterthought.
  * `@nwire/endpoint` makes it the first-class entry point so you don't
  * write the same K8s-readiness code on every project. It works alone —

package/dist/endpoint.js

@@ -28,7 +28,7 @@
  * ## Why this exists
  *
  * Every framework eventually needs a process layer — something that knows
- * about SIGTERM, drains in-flight requests, exposes `/healthz`, and binds
+ * about SIGTERM, drains in-flight requests, exposes `/live`, and binds
  * to a port. Most frameworks bolt this on as a deployment afterthought.
  * `@nwire/endpoint` makes it the first-class entry point so you don't
  * write the same K8s-readiness code on every project. It works alone —
@@ -405,7 +405,7 @@ function printBanner(opts) {
             : `   data:   (no HTTP listener)`,
     ];
     if (opts.probePort !== undefined) {
-        // lightship's actual paths — not /readyz + /healthz (which was a
+        // lightship's actual paths — not /ready + /live (which was a
         // historical misnaming in our docs).
         lines.push(`   probes: http://${opts.host}:${opts.probePort}/live · /ready`);
     }

package/dist/lifecycle.d.ts

@@ -7,13 +7,13 @@
  *     `server.close()`. Without it, in-flight requests on persistent
  *     connections silently die when the process exits.
  *   - **lightship**       — Kubernetes-style readiness/liveness probes on a
- *     separate operational port. Flips `/readyz` to 503 the moment shutdown
+ *     separate operational port. Flips `/ready` to 503 the moment shutdown
  *     starts so the load balancer stops sending new traffic — the single
  *     most important step in a zero-downtime rolling deploy.
  *
  * Sequence on SIGTERM/SIGINT:
  *
- *   1. lightship: /readyz → 503        (LB removes us from rotation)
+ *   1. lightship: /ready → 503        (LB removes us from rotation)
  *   2. wait `drainDelay`               (LB has time to catch up; default 10s)
  *   3. stop accepting new connections  (http-terminator)
  *   4. drain in-flight requests        (http-terminator; bounded by drainTimeout)
@@ -105,7 +105,7 @@ export interface LifecycleManager {
     addCheck(check: HealthCheck): void;
     /**
      * Bare Node http handler for probes-on-main deployments. Mount on your
-     * own HTTP server's /livez and /readyz routes; the third arg picks which.
+     * own HTTP server's /live and /ready routes; the third arg picks which.
      * No framework lock-in — works with Express, Fastify, Koa, raw http.
      */
     probeHandler(req: {

package/dist/lifecycle.js

@@ -7,13 +7,13 @@
  *     `server.close()`. Without it, in-flight requests on persistent
  *     connections silently die when the process exits.
  *   - **lightship**       — Kubernetes-style readiness/liveness probes on a
- *     separate operational port. Flips `/readyz` to 503 the moment shutdown
+ *     separate operational port. Flips `/ready` to 503 the moment shutdown
  *     starts so the load balancer stops sending new traffic — the single
  *     most important step in a zero-downtime rolling deploy.
  *
  * Sequence on SIGTERM/SIGINT:
  *
- *   1. lightship: /readyz → 503        (LB removes us from rotation)
+ *   1. lightship: /ready → 503        (LB removes us from rotation)
  *   2. wait `drainDelay`               (LB has time to catch up; default 10s)
  *   3. stop accepting new connections  (http-terminator)
  *   4. drain in-flight requests        (http-terminator; bounded by drainTimeout)
@@ -53,8 +53,8 @@ export async function attachLifecycle(opts) {
     const healthCfg = {
         enabled: opts.health?.enabled ?? true,
         port: opts.health?.port ?? 9_400,
-        livenessPath: opts.health?.livenessPath ?? "/healthz",
-        readinessPath: opts.health?.readinessPath ?? "/readyz",
+        livenessPath: opts.health?.livenessPath ?? "/live",
+        readinessPath: opts.health?.readinessPath ?? "/ready",
         checks: opts.health?.checks ?? [],
     };
     const terminator = createHttpTerminator({
@@ -138,9 +138,9 @@ export async function attachLifecycle(opts) {
         try {
             if (lightship) {
                 lightship.signalNotReady();
-                console.log(`[lifecycle] /readyz → 503; waiting ${shutdownCfg.drainDelay}ms for LB to catch up`);
+                console.log(`[lifecycle] /ready → 503; waiting ${shutdownCfg.drainDelay}ms for LB to catch up`);
                 // The drain delay exists to give the LB time to redirect traffic
-                // after /readyz flips to 503. Without lightship, there's no probe
+                // after /ready flips to 503. Without lightship, there's no probe
                 // for an LB to poll — waiting would just stall shutdown.
                 await new Promise((r) => setTimeout(r, shutdownCfg.drainDelay));
             }
@@ -166,13 +166,13 @@ export async function attachLifecycle(opts) {
     process.once("SIGTERM", () => void shutdown("SIGTERM"));
     process.once("SIGINT", () => void shutdown("SIGINT"));
     /**
-     * Bare Node http handler for `/livez` / `/readyz` on the MAIN port. Use
+     * Bare Node http handler for `/live` / `/ready` on the MAIN port. Use
      * when probes-on-main is the deployment shape (Cloud Run, Lambda Function
      * URLs, simple K8s sidecar-free setups).
      *
      *   const probeHandler = lifecycle.probeHandler;
-     *   expressApp.get("/livez", (req, res) => probeHandler(req, res, "live"));
-     *   expressApp.get("/readyz", (req, res) => probeHandler(req, res, "ready"));
+     *   expressApp.get("/live", (req, res) => probeHandler(req, res, "live"));
+     *   expressApp.get("/ready", (req, res) => probeHandler(req, res, "ready"));
      *
      * `live` is always 200 unless the process is shutting down.
      * `ready` is 200 only when all checks pass AND we're not shutting down.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nwire/endpoint",
-  "version": "0.10.0",
+  "version": "0.10.1",
   "description": "Nwire — production process lifecycle. Wraps any Node server (Express, Fastify, Koa, Nest, Nwire interfaces) with K8s-grade graceful shutdown, http-terminator drain, and lightship readiness/liveness probes. Standalone — no framework dependency beyond @nwire/container.",
   "keywords": [
     "endpoint",
@@ -32,10 +32,10 @@
   "dependencies": {
     "http-terminator": "^3.2.0",
     "lightship": "^9.0.4",
-    "@nwire/container": "0.10.0",
-    "@nwire/hooks": "0.10.0",
-    "@nwire/wires": "0.10.0",
-    "@nwire/logger": "0.10.0"
+    "@nwire/hooks": "0.10.1",
+    "@nwire/container": "0.10.1",
+    "@nwire/logger": "0.10.1",
+    "@nwire/wires": "0.10.1"
   },
   "devDependencies": {
     "@types/node": "^22.19.9",