fulmine.js 5.21.1 → 5.21.3

package/README.md

@@ -1,6 +1,6 @@
 <img src="./assets/logo-mark.svg" alt="" width="88" align="right">
 
-# Fulmine.js: the drop-in Express 5 replacement, up to 20x faster
+# Fulmine.js: the drop-in Express 5 replacement, up to 22x faster
 
 **Fulmine** (lightning in Italian ⚡) is an Express 5 compatible web framework for Node.js, built on
 [µWebSockets.js](https://github.com/uNetworking/uWebSockets.js) instead of `node:http`. Same API, same
@@ -24,12 +24,12 @@ const express = require("fulmine.js"); // instead of require("express")
 
 ## Why Fulmine
 
-- **Faster than Express, measured.** 1.3x to 4.9x on plain routing, 2x to 5x on a request with a body,
-  7x to 20x on a large route table, on every CI run. Routes are matched in C++ by µWS's own router,
+- **Faster than Express, measured.** 1.2x to 4.5x on plain routing, 1.7x to 5x on a request with a body,
+  7x to 22x on a large route table. Routes are matched in C++ by µWS's own router,
   and a simple enough handler is answered without running any JavaScript at all.
 - **Zero rewrite.** `helmet`, `cors`, `passport`, `morgan`, `multer`, `express-session` and the rest of
   the Express ecosystem keep working. Not "mostly": every test runs against real Express first and the
-  output must match byte for byte, and Express 5's own test suite passes whole, 1130 of 1130.
+  output must match byte for byte, and Express 5's own test suite passes whole.
 - **Your framework works too.** NestJS, Next.js, Astro, SvelteKit, React Router, Angular SSR, Apollo
   Server, tRPC, tsoa, MCP servers: each one is served twice in CI, on Express and on Fulmine, and compared.
 - **Ranked in public.** See [HttpArena](https://www.http-arena.com/#sort=rps:-1&q=Js) and

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "fulmine.js",
-    "version": "5.21.1",
+    "version": "5.21.3",
     "description": "Drop-in Express 5 replacement on uWebSockets.js, up to 20x faster. Same API, your middleware and framework keep working.",
     "main": "src/index.js",
     "exports": {
@@ -164,7 +164,6 @@
         "eslint-plugin-sonarjs": "^4.2.0",
         "etag": "^1.8.1",
         "eventsource": "^5.0.0",
-        "exit-hook": "^5.1.0",
         "express": "^5",
         "express-art-template": "^1.0.1",
         "express-basic-auth": "^1.2.1",

package/src/adopt.js

@@ -14,20 +14,10 @@ See the License for the specific language governing permissions and
 limitations under the License.
 */
 
-// The commands that edit a config file rather than source: `npx fulmine.js override`,
-// `npx fulmine.js angular` and `npx fulmine.js pnpm`.
-//
-// `migrate` rewrites `require("express")` in your own files. The cases it cannot reach are each
-// a line in a config file:
-//
-//   override   A framework built on Express requires it in its own code, so there is no specifier
-//              to rewrite. Every package manager can answer `express` with this package instead,
-//              and each one spells it differently.
-//   angular    An Angular server bundle is built with esbuild, which inlines every dependency and
-//              cannot load uWS's native binary. Two names in `externalDependencies` fix it.
-//   pnpm       pnpm 10.26 and later refuse a git dependency of a dependency, and µWebSockets.js
-//              is one. A direct dependency is allowed, so the project takes it on itself and an
-//              override drops the copy this package asks for.
+// The commands that edit a config file, the cases `migrate` cannot reach by rewriting a specifier:
+//   override   a framework requires express in its own code, so the package manager answers it
+//   angular    the esbuild server bundle cannot inline uWS's binary, two externalDependencies
+//   pnpm       pnpm >= 10.26 refuses a git dependency of a dependency, the project takes it on itself
 
 "use strict";
 
@@ -78,11 +68,8 @@ function indentOf(source) {
 }
 
 /**
- * Reads a JSON file, or explains why it could not be read rather than throwing a parser error.
- *
- * The read is attempted rather than guarded by an existence check: both commands write the file
- * they read, and a check followed by a write to the same path is a race. `code` is what a caller
- * names the missing file by.
+ * Reads a JSON file, or explains why it could not be read. No existence check first, a check
+ * then a write is a race.
  *
  * @param {string} file
  * @returns {{data: any, source: string}|{error: string, code: string|undefined}}
@@ -353,10 +340,9 @@ function withPnpmOverride(source) {
 /**
  * npx fulmine.js pnpm [dir] [--dry-run]
  *
- * Makes a pnpm project install this package, which pnpm 10.26 and later otherwise refuse: the
- * project takes µWebSockets.js as a direct dependency, at the spec this package pins, and an
- * override in pnpm-workspace.yaml drops the copy this package asks for. pnpm 11 reads its
- * settings from that file only, so package.json's `pnpm` field is not where this goes.
+ * Makes a pnpm project install this package: µWebSockets.js as a direct dependency at the pinned
+ * spec, and an override in pnpm-workspace.yaml (the only file pnpm 11 reads) dropping the copy
+ * this package asks for.
  *
  * @param {string[]} argv everything after the command name
  * @returns {number} exit code