Duplicates
Latest version
Summary π‘
With Solid.js 2.0 currently in beta and SolidStart 2.0 in alpha, this might be an opportune time to align both projects.
I also wonder if SolidStart will be migrated to Solid.js v2? After all, the disruptive updates in Solid.js v2 are numerous. I need to make preparations for the migration in advance.
Examples π
No response
Motivation π¦
Current state:
- Solid.js 2.0 is in beta with significant improvements to reactivity primitives and signal semantics
- SolidStart 2.0 is in alpha and actively being developed
- Both have user bases that expect instability during pre-release
Why this matters:
- Avoid double migration: If SolidStart 2.0 stabilizes on Solid.js 1.x first, users would need to migrate twice (Start1β2, then adapting to Solid 2.0)
- Deeper integration: Solid.js 2.0's changes to reactivity internals (owner tracking, signal semantics) could benefit SolidStart's SSR and hydration implementation
- Ecosystem alignment: A synchronized release reduces fragmentation and provides clearer documentation paths
Duplicates
Latest version
Summary π‘
With Solid.js 2.0 currently in beta and SolidStart 2.0 in alpha, this might be an opportune time to align both projects.
I also wonder if SolidStart will be migrated to Solid.js v2? After all, the disruptive updates in Solid.js v2 are numerous. I need to make preparations for the migration in advance.
Examples π
No response
Motivation π¦
Current state:
Why this matters: