Fusion.js SSR render plugin and Koa HTTP server integration: cancellation and timeout propagation

Answer

No. Fusion.js core does not expose a standardized cancellation token that the SSR render plugin and Koa HTTP middleware can both observe. Client disconnect is not automatically propagated to in-flight data-fetching plugins, and there is no canonical framework-level timeout enforcement across the plugin chain.

Confirmed facts

• Fusion.js core provides ctx.request.aborted as a boolean flag that is set when the underlying request/response is closed. It does not provide an AbortSignal or any standardized cancellation token on context.
• Koa server.timeout governs idle socket intervals only. It does not abort or interrupt in-flight plugin middleware, SSR rendering, or data-fetching work.
• The core has no built-in framework timeout wrapper and no enforced plugin contract for deadlines. Fusion.js is in maintenance mode.
• fusion-plugin-universal-events introduces an UniversalEventsToken for cross-boundary cancellation, but it is opt-in and not wired into the core request lifecycle.
• The official render plugin fusion-plugin-react and typical data-fetching plugins may manually inspect ctx.request.aborted if they choose to. There is no framework-level automatic propagation of disconnect signals.

Likely explanation

Without a shared cancellation token, in-flight SSR streams and downstream data-fetching plugins continue to run until they naturally finish or error unless each plugin individually checks ctx.request.aborted or implements its own timeout logic. Timeout enforcement across the plugin chain must be added explicitly via custom middleware or an opt-in package, because the core does not enforce deadlines or provide a unified deadline mechanism. Behavior on client disconnect is undefined and varies by plugin implementation.

Steps needed for this case

1. Verify your Fusion.js version provides ctx.request.aborted. Older releases <=3.x may lack the flag.
2. Audit the render and data-fetching plugins in use for explicit ctx.request.aborted checks and for any AbortSignal usage. If absent, disconnect will not cancel work.
3. Do not rely on Koa server.timeout for request deadlines. It only closes idle sockets.
4. If you need deadline enforcement, add it explicitly at the HTTP layer and propagate a signal/token to plugins yourself. Opt-in packages such as fusion-plugin-universal-events require manual integration to affect core middleware.

One missing diagnostic detail that changes the recommendation: which Fusion.js major version and which render/data-fetching plugins are in use. The presence of ctx.request.aborted and any custom abort handling depends on version and plugin choices.