# The only software that didn’t break this week...

## Executive summary

This report details the release of Solid 2.0, a major framework update that aims to eliminate common frontend issues like race conditions and complex loading states by integrating async data handling directly into the signal system. The release also emphasizes a shift toward AI-driven development, where the framework provides detailed error codes, locations, and suggested fixes specifically tailored for coding agents.

## Key takeaways

- Integrated Async Data Handling: Solid 2.0 allows computations to return a Promise, enabling data fetching within a regular memo and reading the result in JSX, simplifying complex dependency chains (e.g., dropdown preferences fetching based on selection).
- Enhanced Error Reporting for Agents: When Solid encounters an error, it provides an error code, the exact location, a suggested fix, and a path to a `skill.md` file, allowing AI agents to self-correct.
- Refactoring and Consolidation: Solid 2.0 absorbed server functions previously found in Solid Start, leading the developer to 'kill' Solid Start, arguing that Solid now provides all necessary building blocks (state, async, server) independently.
- Rigorous Release Process: The 2.0 beta required 23 release candidates, 971 PRs, and 750 closed issues, with the team refusing to call it stable until a full week passed without regression.

## Technical details

- Signal Mechanism: Unlike Solid 1.0, where signals were synchronous, Solid 2.0 allows async values to behave like any other signal, reducing the need for manual loading flags and mitigating race conditions.
- Framework Architecture: Solid 2.0 is described as 'React: The Good Parts,' utilizing components and JSX, but with a fundamentally different internal mechanism where a component function runs exactly once.
- AI Integration (JetBrains Air): JetBrains Air allows developers to run multiple coding agents (e.g., Claude Code, Codeex, C-Pilot, Juny) side-by-side within the IDE, enabling them to access tools like the debugger and run tests.

## Practical implications

- Developers can reduce boilerplate code related to managing loading states and race conditions in complex data flows.
- The integration of AI agents into the IDE allows for more systematic code review and automated error correction.
- The framework's advanced error tracking (state reading/updating) helps catch issues like request waterfalls and effect loops before production deployment.

## Topics

Frontend Development, React Alternatives, Signals, AI Coding Agents, Build Process, Error Handling, JetBrains Air, Solid 2.0

Source: https://www.youtube.com/watch?v=Qxor6jpfSiU
