@hwip/cli 0.1.24 → 0.1.25

package/dist/http-failure.d.ts

@@ -76,16 +76,26 @@ export interface ProxyConfig {
  *
  * Not through Node's own `http.setGlobalProxyFromEnv`: it exists only from 24.14
  * and 25.4, and the CLI runs on older Nodes. `fetch` gets undici's
- * `EnvHttpProxyAgent` as the global dispatcher (undici 6, Node >= 18.17); `ws`
+ * `EnvHttpProxyAgent` as the global dispatcher (undici 6, Node >= 18.17 — Node 26's
+ * own fetch ignores it; the daemon swaps in undici's fetch, `useHttp1Transport`); `ws`
  * opens its own connection, so it gets a CONNECT-tunnelling agent from
- * `https-proxy-agent` (`webSocketProxyOptions`). Both libraries load only here,
- * so a run with no proxy pays nothing for them.
+ * `https-proxy-agent` (`webSocketProxyOptions`). Both libraries load only here
+ * (undici also in the daemon), so a command run with no proxy pays nothing for them.
  *
  * A proxy that cannot be set up is an error, not a direct connection: going
  * around a proxy someone configured is the wrong way to fail. The error names
  * the setting and never quotes it: the value may carry the proxy's password.
  */
 export declare const useProxyFromEnv: (env?: ProxyEnv, config?: ProxyConfig) => Promise<void>;
+/**
+ * Pin the daemon's `fetch` to HTTP/1.1: an aborted HTTP/2 upload on Node 26 wedged the
+ * event loop in nghttp2's send loop (one shared session); HTTP/1.1 gives each request its
+ * own socket. Node 26's fetch (undici 8) reads `undici.globalDispatcher.2`, undici 6 writes
+ * `.1`, and an undici 6 dispatcher handed to Node 26's fetch fails "invalid onError method"
+ * — so the fetch is swapped for undici 6's own, which also makes `useProxyFromEnv`'s proxy
+ * agent apply again. Daemon only (`cli-lazy-load.test.ts`); call after `useProxyFromEnv`.
+ */
+export declare const useHttp1Transport: () => Promise<void>;
 /**
  * Options for the listener's `new WebSocket`: `ws` opens its own connection
  * and never reaches fetch's dispatcher, so with a proxy set it is handed an

package/dist/http-failure.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.webSocketProxyOptions = exports.useProxyFromEnv = exports.proxyForUrl = exports.AUTH_HINT = exports.httpFailureMessage = exports.readJsonBody = exports.networkFailureMessage = exports.isUnsendableHeader = exports.isConfigFailure = exports.isInvalidUrl = exports.neverConnected = exports.isRedirectRefusal = void 0;
+exports.webSocketProxyOptions = exports.useHttp1Transport = exports.useProxyFromEnv = exports.proxyForUrl = exports.AUTH_HINT = exports.httpFailureMessage = exports.readJsonBody = exports.networkFailureMessage = exports.isUnsendableHeader = exports.isConfigFailure = exports.isInvalidUrl = exports.neverConnected = exports.isRedirectRefusal = void 0;
 const redact_js_1 = require("./redact.js");
 const ws_url_js_1 = require("./ws-url.js");
 /**
@@ -273,10 +273,11 @@ const configProxyValue = (key, config) => {
  *
  * Not through Node's own `http.setGlobalProxyFromEnv`: it exists only from 24.14
  * and 25.4, and the CLI runs on older Nodes. `fetch` gets undici's
- * `EnvHttpProxyAgent` as the global dispatcher (undici 6, Node >= 18.17); `ws`
+ * `EnvHttpProxyAgent` as the global dispatcher (undici 6, Node >= 18.17 — Node 26's
+ * own fetch ignores it; the daemon swaps in undici's fetch, `useHttp1Transport`); `ws`
  * opens its own connection, so it gets a CONNECT-tunnelling agent from
- * `https-proxy-agent` (`webSocketProxyOptions`). Both libraries load only here,
- * so a run with no proxy pays nothing for them.
+ * `https-proxy-agent` (`webSocketProxyOptions`). Both libraries load only here
+ * (undici also in the daemon), so a command run with no proxy pays nothing for them.
  *
  * A proxy that cannot be set up is an error, not a direct connection: going
  * around a proxy someone configured is the wrong way to fail. The error names
@@ -334,6 +335,22 @@ const useProxyFromEnv = async (env = process.env, config = {}) => {
     };
 };
 exports.useProxyFromEnv = useProxyFromEnv;
+/**
+ * Pin the daemon's `fetch` to HTTP/1.1: an aborted HTTP/2 upload on Node 26 wedged the
+ * event loop in nghttp2's send loop (one shared session); HTTP/1.1 gives each request its
+ * own socket. Node 26's fetch (undici 8) reads `undici.globalDispatcher.2`, undici 6 writes
+ * `.1`, and an undici 6 dispatcher handed to Node 26's fetch fails "invalid onError method"
+ * — so the fetch is swapped for undici 6's own, which also makes `useProxyFromEnv`'s proxy
+ * agent apply again. Daemon only (`cli-lazy-load.test.ts`); call after `useProxyFromEnv`.
+ */
+const useHttp1Transport = async () => {
+    const undici = await import('undici');
+    // With a proxy, its agent is already the dispatcher (HTTP/1.1, undici 6's default).
+    if (!active)
+        undici.setGlobalDispatcher(new undici.Agent({ allowH2: false }));
+    globalThis.fetch = undici.fetch;
+};
+exports.useHttp1Transport = useHttp1Transport;
 /**
  * Options for the listener's `new WebSocket`: `ws` opens its own connection
  * and never reaches fetch's dispatcher, so with a proxy set it is handed an

package/dist/listener.js

@@ -6121,6 +6121,7 @@ const handleListener = async (args) => {
             `Tail \`~/.hwip/listener.log\` to follow it, or kill ${otherPid} first.`);
         return 0;
     }
+    await (0, http_failure_js_1.useHttp1Transport)();
     const settings = (0, exports.listenerSettings)(args);
     if ('exit' in settings) {
         console.error(settings.message);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hwip/cli",
-  "version": "0.1.24",
+  "version": "0.1.25",
   "description": "Hwip CLI + push notification SDK for AI agents",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",