Solid Start v1 when vinxi is 0.5
I just want some clarification regarding the solidstart versioning where solid start has been versioned 1+ suggesting it is somewhat ready to be used for development meanwhile vinxi on what solidstart depends on is itself not yet mature and stable. For example my websocket endpoints that worked on 0.4.3 are not working correctly in 0.5. Is the stability only guaranteed for solidjs related functionality or there are no stability guarantees as of yet?
I understand that the websocket issue is upstream to vinxi in nitro: https://github.com/nitrojs/nitro/issues/2171 . However as a developer my efforts of implemeting the websocket endpoint and then loosing that functionality upon upgrading in the future seems like behavior of an unstable API instead of the stability indicated by version numbers of solid-start.
GitHub
nitrojs/nitro
Next Generation Server Toolkit. Create web servers with everything you need and deploy them wherever you prefer. - nitrojs/nitro
6 Replies
Perhaps @Brendonovich or @brenelz may be able to answer this?
I apologize for being a bit too angry and ranting as I was a little sad of having to have "wasted" time in implementing the ws handler, I acknowledge that the websockets feature is indeed in the experimental parts of the server and therefore my expectations of stability are to be disregarded. However I still fear v1 of solidstart being so heavily reliant on vinxi which afaik is still in somewhat beta and unstable API.
i believe we’re moving towards another option for vinxi (i’m just unsure the timeline for that)
Yeah at some point we will move away from Vinxi it's just a slow process
I didn't know web socket support wasn't working
Thanks for the clarification. I would like to contribute in the refactor and would appreciate any starting issues/projects or discussion I should refer to to get started.
The work I've done is on start's
devinxi branch, we don't have a todo list for it yet. I've just been getting the example projects ported over and trying to make them work. It's a lot of in the weeds work that requires knowing how the new Vite Environment APIs work