Is there any way to guarantee rsf{n} endpoints are stable across builds?

[knpwrs]

I noticed that in development, calling a server action resulted in a call to an endpoint like /RSC/F/_/{filepath}/{functionName}.txt; however, when running the production build, those endpoints are more like /RSC/F/assets/rsf0/{functionName}.txt.

That rsf0 bit is generated here:

waku/packages/waku/src/lib/builder/build.ts

Line 198 in c0e1f3f

`${DIST_ASSETS}/rsf${i}`,

The 0 appears to be based on whatever vite chunk the function ends up in, and I can see multiple endpoints in my test build along the lines of 1, 2, etc.

Is there any way to guarantee the stability of these endpoints across builds? What happens if I produce a new build and a server function I was calling ends up in a different vite entry, but someone's client hasn't been refreshed yet and so the client ends up calling the wrong endpoint?

[dai-shi]

but someone's client hasn't been refreshed yet and so the client ends up calling the wrong endpoint?

Good point. I think we should add "hash" like "rsc".

Related: #1037