Experimental tanstack live query: "signal aborted without reason" on page reload

[strblr]

Environment

Bun 1.2.19
Vite 7.1.1
orpc 1.7.11

Reproduction

1. Use experimental_liveOptions from the tanstack integration:

const counter = useQuery(orpc.demo.counter.experimental_liveOptions());

counter is defined like this:

export const counter = base.handler(async function* () {
  let count = 0;
  while (true) {
    yield { count };
    count++;
    await Bun.sleep(1000);
  }
});

2. In vite dev mode, reload the page in the browser

Describe the bug

When reloading the page, this error is intercepted in the client's RPCLink:

AbortError: signal is aborted without reason

The link looks like this:

const link = new RPCLink({
  url: import.meta.env.VITE_API_URL,
  interceptors: [
    onError(error => {
      console.error(error);
    })
  ]
});

Additional context

No response

Logs

[dosubot]

Hi @strblr! I'm Dosu and I’m helping the orpc team.

This error is expected in Vite dev mode when using experimental live queries: reloading the page interrupts ongoing streams, triggering an abort signal for cleanup. The "AbortError: signal is aborted without reason" is not an application bug, but a side effect of how TanStack Query and orpc handle live query teardown during navigation or reloads. This does not affect production builds and is considered safe to ignore in development source.

If you want to reduce console noise, you can filter these abort errors in your interceptor by checking error.name === "AbortError" or error instanceof AbortError before logging. There are no built-in options in orpc or TanStack Query to suppress these specifically, but custom filtering in your onError interceptor is the recommended approach source.

Recent changes to the tanstack-query integration in orpc (PR #840) adjusted how queries are enabled, but do not alter abort signal handling for live queries source.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[strblr]

Turns out when disabling react strict mode, the error is gone. Is this error to be expected or can it be fixed at orpc-level?

[dosubot]

Yes, this error is expected when React Strict Mode is enabled. Strict Mode intentionally causes extra mount/unmount cycles, which triggers abort signals and leads to more frequent "AbortError: signal is aborted without reason" messages during live queries. This is standards-compliant behavior in orpc's TanStack Query integration—abort signals are passed through for proper cleanup when components unmount or reload, and orpc does not suppress or mutate these errors internally (source).

There’s no orpc-level fix or configuration for this; filtering these errors should be done in your app’s error interceptor (for example, by ignoring errors where error.name === "AbortError"). This does not affect production builds, where Strict Mode is typically disabled and these aborts are much less frequent.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[dinwwwh]

Turns out when disabling react strict mode, the error is gone. Is this error to be expected or can it be fixed at orpc-level?

I think oRPC can't help in this case.