Hey, folks!
Here's a cheeky video version if you don't feel like reading.
Today marks a special day for SolidStart. Thanks to our partner Anomaly we now have formed a dedicated task force to raise the bar for our framework and maintenance. It has been some busy and amazing couple of weeks working together with Dax and his team, collecting feedback on their experience and shaping our roadmap. Which I'm happy to share with you below!
As my main task on the Solid's Core team I'll take responsibility in managing feedback and addressing them with the team. But that's just part of our renewed commitment.
Our main priority is replacing Vinxi with a pure Vite-based system, feel free to follow the ongoing work at devinxi branch. Our release plan has 3 steps.
| Release | Milestone |
|---|---|
2.0.0-alpha |
Feature parity reached with current 1.x.x release |
2.0.0-beta |
Support for Solid 2.x.x is achieved |
2.0.0 |
Battle-tested for edge cases and regressions |
We will also work closely with the Docs team to make sure every release is properly documented for migrations.
- The
2.0.0-alphaeffort is being carried by @Brendonovich and @katywings . - Docs and Day-to-Day will be led by @brenelz and myself.
Going forward, we are moving current version of SolidStart to 1.x branch.
DeVinxi work will soon be merged in main.
New features and changes to v1 will require more thorough testing so we can port them to the new architecture as we map and perform 2.0 work.
What about features?
Work has not stopped in improving the developer experience. As an immediate follow-up to DeVinxi work we intend to make Server-Functions easier to use. We will share more on that progress soon enough, meanwhile you can join us in Solid Discord at #solidstart to share feedback and keep tabs on our progress.
It's important to say that with DeVinxi efforts, we're also bound to an update on our infrastructure, before SolidStart 2.0.0 reaches stability, we're aiming to have Nitro updated to v3 and with a more straightforward integration.
Keeping the lights on
At the moment we have many issues that lack triage and a few opened PRs that must be reviewed. We also reckon our documentation could use a touch up and some bulk. This will be added to our ongoing efforts in parallel to the DeVinxi initiative.
@brenelz and I are working with the Docs team to improve your experience using SolidStart, but we could use your help either reaching out to Docs team directly and contributing, or letting us know what are missing spots you're more eager to see covered!
And then what?
With SolidStart 2.0 we are looking into improving the developer experience for streaming and realtime experiences towards the end of 2025 and beginning of the next.
Primitives, not Frameworks
As topsy-turvy as the above quote may sound for a meta-framework, we want to provide you with flexible ergonomics and strong defaults. That has been the cornerstone of everything inside the Solid ecosystem and will remain true for SolidStart. We will remain unopionated but we will still provide users with great features for build your fullstack apps towards the future, bridging the gap and reducing the tradeoffs between Multi-Page Apps (MPAs) and Single-Page Apps (SPAs).
As always, you can find us around here or on discord.gg/solidjs
🤘 All the best,
@atilafassina, @Brendonovich , @brenelz , @katywings , and the Solid team