@aria-framework/kit 0.6.0 → 0.6.1

package/asyncHandler.js

@@ -13,12 +13,22 @@
  *
  * Express 5 handles this natively. Kept anyway: it is a no-op there, and removing it would mean
  * editing every route the day an app upgrades.
+ *
+ * IT RETURNS THE PROMISE, and that `return` is load-bearing even though Express ignores it.
+ * TEST HARNESSES AWAIT THE HANDLER. Both consuming apps drive real route handlers directly —
+ * `await callback(req, res, next)` — to exercise a flow without standing up a server. Drop the
+ * return and `await undefined` resolves immediately, so every assertion runs BEFORE the handler
+ * has finished and a suite that was proving something starts proving nothing.
+ *
+ * This was found the hard way: 0.6.0 shipped without it, because the original was a one-line
+ * arrow whose implicit return was invisible when it was rewritten as a named function. Eight
+ * checks in one app's Entra suite failed, all of them looking like authorisation bugs.
  */
 
 'use strict';
 
 module.exports = function asyncHandler(fn) {
   return function (req, res, next) {
-    Promise.resolve(fn(req, res, next)).catch(next);
+    return Promise.resolve(fn(req, res, next)).catch(next);
   };
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aria-framework/kit",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "description": "Aria App Framework — kit module. Small dependency-free server utilities: open-redirect guard (safeReturnTo), SQL LIKE escaping, magic-byte upload validation (fileSniff), Crockford base32 tracking IDs, and person-name compose/split helpers.",
   "license": "UNLICENSED",
   "private": false,