@bakery-framework/cli 2.2.1 → 2.3.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bakery-framework/cli",
-  "version": "2.2.1",
+  "version": "2.3.0",
   "description": "Bakery entry point and process supervision: mode dispatch, dev watcher, cluster.",
   "keywords": [
     "bakery",
@@ -39,10 +39,10 @@
     "bun": ">=1.4.0"
   },
   "dependencies": {
-    "@bakery-framework/core": "^2.2.1"
+    "@bakery-framework/core": "^2.3.0"
   },
   "peerDependencies": {
-    "@bakery-framework/orm": "^2.2.1"
+    "@bakery-framework/orm": "^2.3.0"
   },
   "peerDependenciesMeta": {
     "@bakery-framework/orm": {

package/src/pipeline.ts

@@ -35,12 +35,40 @@ export type RateLimitConfig = Exclude<ProcessedAppConfig['rateLimit'], false>
  * 400 is included: `>= 400`, not `> 400`. A handler returning a bare
  * `new Response(…, {status: 404})` must still reach `TSXErrorHandler` and get
  * the app's error page rather than an empty body.
+ *
+ * A Response whose body the app wrote as a document is not an error to dress,
+ * whatever its status: `hasOwnDocument`. The registry keeps only the status
+ * of what it replaces, so through 2.2.2 an `onRequest` answering with its own
+ * 404 page came back as the app's `error-404.html` (or Bakery's own page),
+ * and an API route's `Response.json({ error }, { status: 404 })` as an
+ * envelope whose message read `404`.
  */
 export function isErrorResult(res: unknown): boolean {
-  if (res instanceof Response) return res.status >= 400
+  if (res instanceof Response) return res.status >= 400 && !hasOwnDocument(res)
   return is.object(res) && 'errorCode' in res
 }
 
+/**
+ * Whether an error Response carries a document of its own: a body typed as
+ * anything but plain text (an HTML page, a JSON document, an uploaded site's
+ * `404.html`).
+ *
+ * What asks to be dressed is untyped or plain text: `response.error()`, a
+ * null body, and a string body such as the router's own
+ * `new Response('Not Found', { status: 404 })`, which Bun leaves untyped until
+ * it is sent. Those still get the app's error page, or the JSON envelope under
+ * `/api`.
+ *
+ * The header alone, never `res.body`: on Bun 1.4.2 reading the body of a Blob
+ * or file Response first makes its `content-type` read `null`, so
+ * `new Response(Bun.file('404.html'), { status: 404 })` would be judged
+ * untyped and dressed.
+ */
+export function hasOwnDocument(res: Response): boolean {
+  const type = res.headers.get('content-type')
+  return Boolean(type) && !/^text\/plain\b/i.test(type!)
+}
+
 /**
  * One bucket a request can be charged to: the top level, or a route rule,
  * checked and ready to match.

package/src/worker.ts

@@ -305,6 +305,11 @@ try {
               Bakery.sharedPool.incrementCounter(COUNTER_SLOTS.TOTAL_ERRORS, 1)
               return await handleRequestError(path, req, res)
             }
+            // The app's own error page (see `hasOwnDocument`): sent as written,
+            // and still an error answer for the counter.
+            if (res instanceof Response && res.status >= 400) {
+              Bakery.sharedPool.incrementCounter(COUNTER_SLOTS.TOTAL_ERRORS, 1)
+            }
             return res
           },