Run on node:http, node:http2, Bun and Deno

The app is a request listener like Express's, so http.createServer(app) works, and with it supertest. Node serves those requests, not uWS: it is for compatibility, not for speed. On Bun and Deno app.listen() takes this path by itself.

From a clone of the repository:

cd examples && npm install
node node-http.js

// The app is a request listener like Express's, so http.createServer(app) works, and with it
// supertest, vhost and anything else that calls an app. Node serves these requests, not µWS: it is
// for compatibility, not for speed. On Bun and Deno, app.listen() takes this path by itself.
//
//   node node-http.js
//   curl http://localhost:3000/
const http = require("node:http");
const express = require("fulmine.js"); // instead of require("express")

const app = express();

// isFulmine is true here and undefined on Express, for code that runs on both
app.get("/", (req, res) => {
    res.send(express.isFulmine ? "fulmine.js through node:http" : "express");
});

http.createServer(app).listen(3000, () => console.log("http://localhost:3000/"));

HTTP/2

Express crashes on node:http2, so http2-express-bridge exists. Fulmine does not need it, the app is a listener for http2.createServer and http2.createSecureServer too. With allowHTTP1: true the same port also answers HTTP/1.1. Also here node serves the requests, not µWS: µWS has no HTTP/2.

const http2 = require("node:http2");
const fs = require("node:fs");

http2
    .createSecureServer(
        { key: fs.readFileSync("server.key"), cert: fs.readFileSync("server.crt"), allowHTTP1: true },
        app
    )
    .listen(8443);

On HTTP/2, :authority is read as Host when the client sends no Host, req.httpVersion is "2.0", and the connection headers (Connection, Keep-Alive) are not written, the protocol forbids them.

Run on node:http, node:http2, Bun and Deno ​

HTTP/2 ​

Run on node:http, node:http2, Bun and Deno

HTTP/2