fulmine: 5.11.0, and /pipeline written so it compiles

frameworks/fulmine/README.md

@@ -30,7 +30,9 @@ because they are where the framework differs from Express rather than where it i
 - Routes with a parameter, `/json/:count` among them, are handed to the µWS router rather than
   matched in JavaScript.
 - A handler simple enough to be read at registration time is compiled into a µWS declarative
-  response. `/pipeline` is one, so it is answered without entering JavaScript.
+  response. `/pipeline` is one, so it is answered without entering JavaScript. "Simple enough" means
+  every argument is a literal, which is why its headers are written out instead of coming from the
+  shared `SERVER_HDR`: the compiler reads the source and cannot see into a closure.
 - `express.compression()` is the framework's own, taking the compression module's options: it is
   mounted on the json route, which is the only one the profiles ask to compress.
 - `express.static(dir, { preCompressed: true })` is the framework's documented way of serving the

frameworks/fulmine/app.js

@@ -127,8 +127,12 @@ function sumQuery(query) {
     return sum;
 }
 
+// Written out rather than through SERVER_HDR, and that is the whole of it: with every argument a
+// literal, the framework compiles this handler into a uWS declarative response at listen() and the
+// route is answered without entering JavaScript. A closure it cannot read keeps it on the ordinary
+// path, which is what SERVER_HDR was doing here.
 app.get('/pipeline', (req, res) => {
-    res.set(SERVER_HDR).type('text/plain').send('ok');
+    res.set({ 'server': 'fulmine' }).type('text/plain').send('ok');
 });
 
 // shared by the plaintext listener and the TLS one on 8081: same handler, same shapes

frameworks/fulmine/package.json

@@ -2,7 +2,7 @@
   "name": "httparena-fulmine",
   "private": true,
   "dependencies": {
-    "fulmine.js": "^5.9.0",
+    "fulmine.js": "^5.11.0",
     "pg": "^8.13.0",
     "pg-native": "^3.8.0",
     "ejs": "^3.1.10",