Issues with New RPC Conversion and Documentation Concerns
Over the last few hours I have been converting my app to use the new RPC, and I gotta say that I have had some problems 
The websocket problem turned out to be related to nitro and tanstack (I still don't fully know why?)
But during me trying to convert everything I've found some problems that are quite the roadblock. I'll list them, maybe someone knows what's up.
The application is a fullstack application, so in the backend when prefetching I'd like to naturally not call the HTTP API, but instead directly call the rpc method directly. Sadly it seems that every time I get:
I've tried to integrate the websocket in the browser and have failed in doing so - my expectation was that using a
I have some layers that return Stream, but obv. in the frontend I can't really use them as such, so I do:
turns out the result is always
I can of course just return an
What I liked about the previous approach of defining rpc routes was that they were separate from each other, with the current layer approach, whenever I get a single error the whole block turns red, which is super frustrating and hard to debug.
Additionally the docs for trying to set-up the rpc was a bit confusing, so I did a bunch of of guesswork, specifically https://github.com/Effect-TS/effect/tree/main/packages/rpc#serving-the-api is still from the old version.
The websocket problem turned out to be related to nitro and tanstack (I still don't fully know why?)
But during me trying to convert everything I've found some problems that are quite the roadblock. I'll list them, maybe someone knows what's up.
RpcTest
The application is a fullstack application, so in the backend when prefetching I'd like to naturally not call the HTTP API, but instead directly call the rpc method directly. Sadly it seems that every time I get:
WebSocket
I've tried to integrate the websocket in the browser and have failed in doing so - my expectation was that using a
ManagedRuntimefromWebSocketThis specifically I tested with a standalone Bun server
Http Streams
I have some layers that return Stream, but obv. in the frontend I can't really use them as such, so I do:
turns out the result is always
[]StreamI can of course just return an
ArraylayerNdJsonDX concerns
What I liked about the previous approach of defining rpc routes was that they were separate from each other, with the current layer approach, whenever I get a single error the whole block turns red, which is super frustrating and hard to debug.
Additionally the docs for trying to set-up the rpc was a bit confusing, so I did a bunch of of guesswork, specifically https://github.com/Effect-TS/effect/tree/main/packages/rpc#serving-the-api is still from the old version.
Was this page helpful?
