dsh-unlag 1.9.110 → 1.9.112

package/README.md

@@ -76,6 +76,17 @@ dsh plugin install dsh-unlag
 - 状态：`GET /dsh-unlag/state` → `{"version":"<当前版本>","code":"<index.js 写入时间>","plugins":true,"page":true,"shim":{...}}`。`code` 用来分清「版本号没刷」和「旧代码真的还在跑」。
 - 重建后的日志带起页面代次：`interface rebuilt; the page runs the plugins as served now (page <rev>)`，据此判断新文档加载的是新脚本还是旧脚本。
 
+## 改完后让运行中的 App 用上
+
+不用重启 App，也不用重启页面：换掉 `index.js` 后让插件的记录重载一次即可。
+
+1. 改版本号，并 `touch index.js client.js`。**只改版本号是不够的**：插件的装载按文件时间判断要不要重新读，时间没变就还是旧代码在跑，`/state` 里会看到版本号没变（或变了但 `code` 是旧的）。
+2. 在插件列表里把本插件关掉再打开。这两步之后 `~/.dsh/unlag-reload.log` 会出现一行新的 `dsh-unlag <版本>`。
+3. 等约 20 秒，读 `GET /dsh-unlag/state`：`version` 是新版本、`code` 是刚才 `index.js` 的写入时间，才算真的换上了。
+4. `npm run live-smoke` 对着运行中的 App 复核一遍（见下一节）。
+
+页面那一半（按钮点击后的重建）不在这一步里：那是按钮本人的事，只有人能按。
+
 ## 测试
 
 ```sh

package/index.js

@@ -2032,7 +2032,7 @@ function serveButton(ctx, controller, config) {
   const disposers = []
   for (const [path, handler] of handlers) {
     try {
-      const dispose = server.register({ kind: 'exact', path, handler })
+      const dispose = server.register({ kind: 'exact', path, handler: guardRoute(path, handler) })
       if (typeof dispose === 'function') disposers.push(dispose)
     } catch (error) {
       log(`cannot answer ${path}: ${error?.message ?? error}`)
@@ -2043,6 +2043,44 @@ function serveButton(ctx, controller, config) {
   }
 }
 
+/**
+ * Nothing a route body does may reach the server as a rejection or a throw: an answer that never
+ * settles is a page that waits forever, and a rejected handler can take down the request instead of
+ * saying what happened. Each body already answers from its own guard; this one is the floor under
+ * them, so a future edit that misses a path still costs a status rather than the answer.
+ */
+export function guardRoute(path, handler) {
+  /**
+   * Nothing a route body does may reach the server as a rejection or a throw: an answer that never
+   * settles is a page that waits forever, and a rejected handler can take the request down instead
+   * of saying what happened. Each body answers from its own guard already; this is the floor under
+   * them, so a future edit that misses a path costs a status rather than the answer.
+   */
+  return (req, res) => {
+    const fallback = (error) => {
+      log(`cannot answer ${path}: ${error?.message ?? error}`)
+      try {
+        if (res?.headersSent !== true) sendJson(res, 503, { status: 'error' })
+        else if (res?.writableEnded !== true && res?.destroyed !== true) res.end()
+      } catch {
+        /* the response is already gone; the log line is what is left to say */
+      }
+    }
+    try {
+      const answer = handler(req, res)
+      // The answer is handed back as it came: a caller that waits on the body still waits on it,
+      // and the rejection is watched here as well rather than instead.
+      if (answer !== null && typeof answer === 'object' && typeof answer.then === 'function') {
+        answer.then(undefined, fallback)
+      }
+      return answer
+    } catch (error) {
+      fallback(error)
+      return undefined
+    }
+  }
+}
+
 export function apply(ctx, config) {
   try {
     const instance = {}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-unlag",
-  "version": "1.9.110",
+  "version": "1.9.112",
   "type": "module",
   "description": "A press applies plugin edits right away and brings a laggy interface back; automatic reloading stays off unless you turn it on, so the press is the only trigger, and nothing restarts.",
   "license": "MIT",