Sign In

@ultimat3/http

Package Overview
Dependencies
Maintainers
1
Versions
21
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@ultimat3/http - npm Package Compare versions

Comparing version
11.1.0
to
11.2.0
+5
-5
package.json
{
"name": "@ultimat3/http",
"version": "11.1.0",
"version": "11.2.0",
"description": "Owned request lifecycle over Bun.serve: router, ordered pipeline, problem+json errors",

@@ -34,7 +34,7 @@ "license": "MIT",

"dependencies": {
"@ultimat3/core": "11.1.0",
"@ultimat3/i18n": "11.1.0",
"@ultimat3/schema": "11.1.0",
"@ultimat3/time": "11.1.0"
"@ultimat3/core": "11.2.0",
"@ultimat3/i18n": "11.2.0",
"@ultimat3/schema": "11.2.0",
"@ultimat3/time": "11.2.0"
}
}

@@ -63,2 +63,6 @@ // The one place a framework error code becomes an HTTP status. A table, not a

X_OVERLOADED: 503,
// Core's flight gate refusing past `maxQueued` is the same answer one tier down: it carries
// `retryAfterSeconds` in `meta`, which `stages.ts` renders onto `Retry-After`, so a caller that
// already handles a shed request needs no second branch for a refused one.
X_FLIGHT_GATE_OVERLOADED: 503,
// 403 and never 401: the caller IS authenticated — that is what makes the forged write work —

@@ -231,2 +235,7 @@ // so a 401 would send a signed-in user to a sign-in page they are already past.

X_ABORTED: 499,
// The twin of `X_ABORTED`, and it answers the same because the outcome is the same: the caller
// went away there, the caller's generation moved on here, and in both cases nobody will act on
// the answer. Deliberately not 409 — that spelling asks the client to reconcile and try again,
// and a fenced answer has nothing to reconcile against.
X_SUPERSEDED: 499,
X_INTERNAL: 500,

@@ -233,0 +242,0 @@ // The keys are LITERAL — deliberately not `Readonly<Record<string, number>>`, which is what the