Today, let’s talk honestly about Solid.js’s version support policy. Spoiler alert: it might not be what you expect. But that’s okay. Let’s take a closer look.
When considering a new framework for your project, one of the first questions that comes to mind is: “How long will this technology be supported?” If you’ve worked with technologies like Node.js or Angular that have clear support timelines, you naturally expect similar policies from other frameworks.
1. What is Solid.js?
Before diving into version policies, here’s a quick introduction to Solid.js.
Solid.js is a reactive JavaScript UI library that provides modern framework features like JSX while achieving exceptional performance through direct DOM manipulation without a Virtual DOM. Think of it as looking like React but running much faster.
Solid is a purely reactive library designed from the ground up with a reactive core, influenced by reactive principles from libraries like Knockout. While the syntax resembles React’s functional components, it’s fundamentally different: components execute only once, and only the necessary parts update when changes occur.
Ryan Carniato started the first commit on August 21, 2016, and after about five years of development, version 1.0 was officially released in June 2021. It’s distributed as an open-source project under the MIT License.
2. The Bottom Line – No Official LTS/EOL Policy
Let me be straightforward: Solid.js does not have an official LTS (Long Term Support), EOL (End of Life), or EOS (End of Support) policy like Node.js or Angular.
This isn’t unique to Solid.js. Most frontend frameworks including React, Vue, and Svelte follow the same pattern. Unlike enterprise software that states “supported until December 31, 2025,” these frameworks follow a community-driven, flexible development approach.
But don’t worry. The absence of an official policy doesn’t mean lack of maintenance. The actual release patterns show how steadily Solid.js has been evolving.
3. Complete Solid.js Version History
While there’s no official policy, analyzing the release history reveals Solid.js’s development patterns and stability. Here’s a comprehensive list based on GitHub release records.
Complete Major 1.x Version List
| Version | Release Date | Codename | Key Features | Current Status |
|---|---|---|---|---|
| v1.9.9 | November 2024 | – | Latest stabilization and bug fixes | ✅ Latest (Active) |
| v1.9.0 | September 24, 2024 | LGTM! | Improved JSX validation, custom element enhancements | ✅ Active |
| v1.8.0 | October 9, 2023 | Bifröst | SSR consolidation, serialization optimization | ✅ Active |
| v1.7.0 | March 30, 2023 | U Can’t Type This | TypeScript improvements, catchError added | ✅ Active |
| v1.6.0 | November 2022 | Castle in the Sky | Partial hydration, Islands support | ✅ Active |
| v1.5.0 | July 2022 | Batch to the Future | New batching behavior, keyed control flow | ✅ Active |
| v1.4.0 | May 2022 | Level Up! | Top-level array stores, resource improvements | ✅ Active |
| v1.3.0 | January 2022 | Spice Must Flow | HTML streaming, error boundaries | ✅ Active |
| v1.2.0 | November 2021 | Masters of the Universe | Custom renderers, universal JSX | ✅ Active |
| v1.1.0 | July 2021 | Interrupting Cow | Concurrent rendering, createUniqueId | ✅ Active |
| v1.0.0 | June 28, 2021 | First Major | API stabilization, official release | ✅ Active |
Source: Solid.js GitHub Releases
The 0.x Era (Pre-1.0)
| Version Range | Period | Characteristics |
|---|---|---|
| v0.27.x | Early 2021 | Release candidates before 1.0 |
| v0.26.x | 2020 | Stabilization work |
| v0.10.x ~ 0.25.x | 2019-2020 | Active development phase |
| v0.1.x ~ 0.9.x | 2018-2019 | Early prototypes and experiments |
There were significant syntax changes after version 0.10.3, and starting from 0.27.x, versions were preparing for 1.0 compatibility.
4. Version Support Status – Real-World Situation
While there are no official EOL dates, here’s what versions are actually usable.
Current Support Status (As of October 2025)
| Status | Version | Description |
|---|---|---|
| 🟢 Recommended | v1.9.x | Latest features and bug fixes |
| 🟢 Stable | v1.7.x ~ 1.8.x | Production-ready |
| 🟡 Usable | v1.0.x ~ 1.6.x | Works but missing latest features |
| 🔴 Not Recommended | v0.x | Syntax differences, compatibility issues |
Browser and Runtime Support Policy
Solid.js supports the last 2 years of modern browsers including Firefox, Safari, Chrome, and Edge for both desktop and mobile devices, with no support for IE or other deprecated browsers.
| Environment | Supported Versions |
|---|---|
| Browsers | Last 2 years (Chrome, Firefox, Safari, Edge) |
| Node.js | LTS versions (currently 18.x, 20.x, 22.x) |
| Deno | Latest version |
| Cloudflare Workers | Latest runtime |
| IE11 | ❌ Not supported |
Source: Solid.js npm page
5. Solid.js 2.0 – The Next Major Version
The Solid.js team is currently working on version 2.0, publicly developing experimental features through @solidjs/signals. However, no specific release date has been announced.
Expected Changes in 2.0
- Improved reactive system
- Optimized props and JSX handling
- Simpler API
- Performance improvements
The development team stated that “we’re in the experimental stage with no concrete timeline, which will depend on community help and feedback”.
Source: The Road to 2.0 Discussion
6. Framework Comparison – Support Policy Differences
Major Framework Support Policy Comparison
| Framework | LTS Policy | EOL Specified | Characteristics |
|---|---|---|---|
| Angular | ✅ Yes (18 months) | ✅ Clear | Major version every 6 months |
| Node.js | ✅ Yes (30 months) | ✅ Clear | Enterprise-focused |
| React | ❌ No | ❌ No | Community-driven |
| Vue.js | 🟡 Partial (Vue 2 only) | 🟡 Partial | Vue 2 EOL: Dec 31, 2023 |
| Svelte | ❌ No | ❌ No | Community-driven |
| Solid.js | ❌ No | ❌ No | Community-driven |
Pattern Analysis
With Official Policy (Angular, Node.js)
- Clear end-of-support dates
- Predictable upgrade cycles
- Suitable for enterprise environments
Community-Driven (React, Vue, Solid.js, Svelte)
- Flexible development pace
- User feedback-centric
- Faster innovation possible
7. Considerations for Adopting Solid.js
Advantages
1. Proven Long-term Stability
- Maintained 1.x version for over 3 years since 2021
- Emphasis on API backward compatibility
- Gradual feature additions
2. Active Community
- GitHub Stars: 32,000+
- Active Discord community
- Over 1 million weekly npm downloads
3. Exceptional Performance Consistently ranks at the top in benchmarks, with performance nearly indistinguishable from optimized vanilla JavaScript
4. Transparent Development Process
- All development is public
- Community decision-making through RFCs
Cautions
1. No Clear End-of-Support Date
- Difficult to predict long-term support
- Uncertainty in long-term project planning
2. Relatively Smaller Ecosystem
- Fewer third-party libraries compared to React or Vue
- Potential lack of some integration tools
3. No Commercial Support Options
- No paid technical support
- No enterprise SLAs
4. 2.0 Migration Preparation Needed
- Breaking changes expected in future major updates
- Migration costs to consider
8. Community and Ecosystem Status
Key Metrics (As of October 2025)
| Metric | Value |
|---|---|
| GitHub Stars | 32,000+ |
| Weekly npm Downloads | 1,000,000+ |
| Discord Members | Active community |
| Related Packages (npm) | 862 |
Recent Major Milestones
SolidStart 1.0 was officially released in May 2024, and the project is receiving financial support from the Google Chrome team for performance optimization.
Source: SolidJS X(Twitter)
9. Project Suitability Assessment
Good Fit For
✅ Performance-Critical Projects
- Dashboards, data visualization
- Applications with frequent real-time updates
✅ Flexible Teams
- Open to adopting new technologies
- Can respond quickly to changes
✅ Teams with React Experience
- Similar syntax means lower learning curve
- Relatively easy migration
✅ Prototypes and MVPs
- Fast development speed
- Less code required
Consider Carefully For
⚠️ Large Enterprise Projects
- Need for clear support policies
- Long-term maintenance planning is critical
⚠️ Rich Ecosystem Requirements
- Need for diverse third-party libraries
- Preference for proven solutions
⚠️ Conservative Tech Stacks
- Stability as top priority
- Only use well-established technologies
⚠️ Tech Debt Concerns
- Long-term maintenance perspective
- Developer hiring considerations
10. Version Management Recommendations
Pinning Versions in package.json
{
"dependencies": {
"solid-js": "~1.9.0"
}
}
Version Notation Meanings:
~1.9.0: Allow 1.9.x patch versions only^1.9.0: Allow 1.x.x minor versions (recommended)1.9.0: Exactly 1.9.0 only
Regular Monitoring
- Monthly: Check GitHub Releases
- Review new features: Read CHANGELOG
- Watch for breaking changes
Safe Upgrade Process
- Review release notes
- Apply in test environment first
- Run E2E tests
- Gradual deployment (Canary, Blue-Green)
- Monitor and prepare rollback
11. Release Pattern Analysis
Version Update Cycles
| Update Type | Average Cycle | Characteristics |
|---|---|---|
| Patch (1.9.8 → 1.9.9) | As needed | Bug fixes, small improvements |
| Minor (1.8 → 1.9) | 3-6 months | New features, backward compatible |
| Major (1.x → 2.0) | Unpredictable | Includes breaking changes |
Stability Indicators
Since the 1.0 release, the 1.x version line has been maintained for over 3 years, demonstrating the importance placed on API backward compatibility. This is a positive signal for teams seeking stable development.
Conclusion
While Solid.js lacks a clear LTS/EOL policy, it’s far from an unstable framework. It has proven API stability by maintaining the 1.x version for over 3 years, and continues building trust through an active community and transparent development process.
What matters most is your project’s situation. If performance and modern technology are priorities and your team can adapt flexibly to changes, Solid.js is an excellent choice. However, if guaranteed long-term support is essential, consider Angular or frameworks with more mature ecosystems.
The “right tool” is the one that best fits your project requirements. I hope this article helps you understand Solid.js’s current state and choose the appropriate technology for your project.
References
- Solid.js Official Site
- Solid.js GitHub Repository
- Solid.js GitHub Releases
- Solid.js Official Documentation
- Solid.js Discord Community
- Solid.js npm Page