TanStack•11mo ago•

14 replies

brilliant-lime

Sharing data between `ws` implementation and `createServerFn` util

So I followed this guide https://nize.ph/blog/tanstack-start-websockets/ to implement websockets in my Start application, but I'm having some trouble being able to share data between the WS server, and some server-side routes created with

createServerFn

createServerFn

. My goal is to have the ability to send a websocket message from a server function. The way I've tried to do this, is to create a

Map()

Map()

instance, in which I place websocket "peers", and then I'm attemting to retreive the appropriate peer from the server-side function. However, the Map isn't shared, it seems like the file where

createServerFn

createServerFn

is located, is loaded dynamically by Start, which means the Map is always a new instance rather than being the existing one.

TL;DR on code:
-

src/lib/peerManager.ts

src/lib/peerManager.ts

exports a singleton

export const peerManager = new PeerManager();

export const peerManager = new PeerManager();

src/ws.tsx

src/ws.tsx

imports the singleton, handles websocket, works great
-

src/lib/websocket.ts

src/lib/websocket.ts

imports the singleton but only actually imports it when receiving a request, and it's always a new instance
-

src/routes/user.tsx

src/routes/user.tsx

calls websocket.ts' function and that triggers creating a new instance without the expected peers in it.

Full code: https://stackblitz.com/edit/start-websocket-issue

Nota Bene: The peerManager was how I felt was the "only" way to share data between the websocket implementation, and the user context for a logged in user - I'm using
Clerk
Clerk
for auth if that matters. This maybe be an x/y problem and someone can tell me how to share a session/context between the WS and createServerFn without this peer mapping. I'm not attached to the mapping solution, it's just what I thought might work!

TanStack•11mo ago•

14 replies

brilliant-lime

Sharing data between `ws` implementation and `createServerFn` util

createServerFn

createServerFn

. My goal is to have the ability to send a websocket message from a server function. The way I've tried to do this, is to create a

Map()

Map()

instance, in which I place websocket "peers", and then I'm attemting to retreive the appropriate peer from the server-side function. However, the Map isn't shared, it seems like the file where

createServerFn

createServerFn

is located, is loaded dynamically by Start, which means the Map is always a new instance rather than being the existing one.

TL;DR on code:
-

src/lib/peerManager.ts

src/lib/peerManager.ts

exports a singleton

export const peerManager = new PeerManager();

export const peerManager = new PeerManager();

src/ws.tsx

src/ws.tsx

imports the singleton, handles websocket, works great
-

src/lib/websocket.ts

src/lib/websocket.ts

imports the singleton but only actually imports it when receiving a request, and it's always a new instance
-

src/routes/user.tsx

src/routes/user.tsx

calls websocket.ts' function and that triggers creating a new instance without the expected peers in it.

Full code: https://stackblitz.com/edit/start-websocket-issue

Nota Bene: The peerManager was how I felt was the "only" way to share data between the websocket implementation, and the user context for a logged in user - I'm using
Clerk
Clerk
for auth if that matters. This maybe be an x/y problem and someone can tell me how to share a session/context between the WS and createServerFn without this peer mapping. I'm not attached to the mapping solution, it's just what I thought might work!

Sharing data between `ws` implementation and `createServerFn` util

Similar Threads

Sharing data between `ws` implementation and `createServerFn` util

Similar Threads

Similar Threads

Similar Threads