Thanks. Updated!

They would work. But the problem is that I have no way to fix the TRPCClientError: Operation ended prematurely. So it hard for me to distinguish if the server execution has error or not.

@KATT Calling Alex for help 🥇

@Dealerpriest Having wsLink active throughout the lifetime of the TRPCProxyClient will overload the server with the WebSocket connections.

In my application scenario, I need a web socket connection only for specific routes and I need the client to request the web socket connection only for those route requests. Since the TRPCProxyClient is making the wsLink active in the initialization, my server is getting connected irrespective of the routes.

I raised this #4725. It would be really helpful if you can provide me with some solution.

Feel free to make a pr that makes the subscription 'lazy' and connects on demand

Haha we can do complete but on the client side there's always an error being thrown.

Currently I hacked it by using emit.error with the error message as an enum

@addlistener If you unsubcribe in the onStopped function the subscription will end (is disconnected) before the error is processed (onError is not called).

Like this:

    const subscription = await client.job.tail.subscribe(input, {
      onData(data) {
        process.stdout.write(data.toString());
        process.stderr.write('\n');
      },
      onError(error) {
        process.stderr.write(error.toString());
        process.stderr.write('\n');
      },
      onComplete() {
        process.stderr.write('Done\n');
      },
      onStopped() {
        subscription.unsubscribe();
      },
    });

This works following an emit.complete() from the server

@BickfordA The problem is that, the complete event needs to be triggered from the server. In your example it's still triggered from a client unsub if I understand you correctly.

I can always make a complex workaround but it's just less desirable.

@addlistener The emit.complete() is triggered from the server in my example.

Try adding the unsubcribe to your onStopped example. I think this should prevent the onError from being called as the connection is closed before it is processed.

  const sub =  tClient.testConnection.progress.subscribe({
      emitterId,
    }, {
      onData: (d) => {
        // console.log('on data', d);
        setLog((l) => l + d);
      },
      onError: (e) => {
        console.log('on error', e);
        console.error(e);
        setForceEdit(true);
      },
      onStopped: () => {
        sub.unsubscribe();
        console.log('on stopped');
      }
    });
  return sub;