RSC function API endpoints

[rmarscher]

It could be useful to be able to define RSC API endpoints with fixed URLs. Currently, the server routes created for handling RSC page requests and function calls are internal to Waku. They are different between dev and production and can change between production builds.

I'd like to try using RSC instead of a JSON API. It would also be nice to have the RSC endpoint be available even if I don't have a client component that imports it.

[dai-shi]

I think it's the detail that is not disclosed for users. It shouldn't be guaranteed. I believe RSC API is frontend or BFF. It's not reusable backend.
The idea might change in the future, but at the moment there's no plan.

Currently, the server routes created for handling RSC page requests and function calls are internal to Waku.

Though, I'm not sure what you're referring. Isn't it about RSC server functions?

[rmarscher]

I think it's the detail that is not disclosed for users. It shouldn't be guaranteed. I believe RSC API is frontend or BFF. It's not reusable backend. The idea might change in the future, but at the moment there's no plan.

Yeah, I can understand that it is too tied to bundling to be very reusable. And there is no spec for a client to know how to import an externally hosted server function. OK. Scratch that idea. 😄

Currently, the server routes created for handling RSC page requests and function calls are internal to Waku.

Though, I'm not sure what you're referring. Isn't it about RSC server functions?

Yes. I was just noting that RSC page requests also have internal routing.