Looks great!
I build something similar (vramework.dev), actually on my way now to give a talk on it
Got a presentation for it at presentation.vramework.dev if anyone is interested
I build something similar (vramework.dev), actually on my way now to give a talk on it
Got a presentation for it at presentation.vramework.dev if anyone is interested
Also abstracts away the idea of an eventbus which is pretty critical in any Websocket deployment.
It doesn’t use Websocket directly via Vercel, but would work if you use nextjs by providing it a http server and also providing that server to ws
Can get this to work, but I’m pretty curious why you think this is a game changer? Thanks!
Maybe game changer is an exaggeration but In the vercel community, ws has been a top requested feature for years. See comments on https://x.com/rauchg/status/1872729115595587627
Note to self: need to signup to X!
If deploying off of vercel is acceptable, it can be done pretty nicely via serverless-nextjs or nextjs docker in one server. But from what I understand vercel internally does quite a bit of code analysis to split things and I don't really want to get too deep into the weeds in that direction
Thank you for raising!
Also is running on vercel a requirement?
It’s used in three companies so far, but the new productised (via the cli) version is still in development / qa stages
There is one company that has been using it for over four years tho! Just checked in and seems to be working solid