-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: only one process for the server #4
Comments
Hmm, that’s really, really interesting. I had not thought about a bun plugin to apply the conditions for the framework itself. This sounds promising; I will look into that over the weekend. If you want some references to maybe figure out those weird behaviors in the meantime, Kotekan has a similar setup. |
It would also help if someone can implement the option to add conditions for resolve in bun: |
I did look at Kotekan but this implementation is using the multiple process architecture. My current implementation needs only one process and supports hot reloading in the dev mode |
Yeah, I only mentioned in case you wanted to have a different reference to the rendering process. |
Hi Rafael,
you did an amazing job in getting this working!!
Have a look at my changes to your rss.ts and rsc.ts which allow to only have one running process and bun.serve as the http server:
https://github.com/aheissenberger/r19/tree/bon-one-server
The new server is in
ssr-bun.ts
. Pages can be build withbun run bunbuild
and then starte the server withbun start
rsc-conditions-plugin
will include thersc-bun.rsc.ts
file with the conditionreact-server
?__RSA
to return rsc json codeproblems:
TypeError: Expected Sink
on first call - fixed it with removing streamingnext planned steps:
The text was updated successfully, but these errors were encountered: