solidjs-knowledge-patch

Name: solidjs-knowledge-patch
Availability: InStock
Author: Nevaberry

...

22|Updated Jan 22, 2026

Search Tags:#migration #reactivity #solidjs #solidstart #knowledge-patch #devinxi #api-renames

Ready to run

npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill solidjs-knowledge-patch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: solidjs-knowledge-patch
Source: https://github.com/Nevaberry/nevaberry-plugins/tree/main/plugins/solidjs-knowledge-patch/skills/solidjs-knowledge-patch
Command: npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill solidjs-knowledge-patch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SolidJS knowledge often lags behind major releases; this skill compiles updates from 1.9 to 2.0 beta and SolidStart 1.1 into a concise patch guide.

Core Features & Use Cases

API renames and import changes: maps 1.x APIs to 2.0 equivalents and highlights new import paths.
Reactivity model updates: explains microtask batching, split effects, and async-first computations, with guidance for migration.
Migration scenarios: covers migrations for Loading/Errored boundaries, draft-first stores, and optimistic updates, plus DOM cleanup notes.

Quick Start

Update your SolidJS project to adopt 2.0 beta reactivity and SolidStart 1.1 conventions.

Frequently Asked Questions about solidjs-knowledge-patch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate SolidJS 1.x APIs to 2.0 beta equivalents?▼

Migrating SolidJS 1.x APIs to 2.0 beta requires mapping deprecated constructs to their new equivalents and updating import paths. This patch provides specific API rename mappings and migration guidance for upgrading projects to the new reactivity model.

What reactivity model updates are in SolidJS 2.0 beta?▼

SolidJS 2.0 beta reactivity introduces microtask batching, split effects, and async-first computations. These updates change how batched updates and asynchronous computations are handled, requiring adjustments to existing effect logic during migration.

Does SolidStart 1.1 change loading and error boundary semantics?▼

SolidStart 1.1 changes loading and error boundary semantics, requiring migration scenarios for existing boundaries. The patch covers how to handle these boundary updates along with draft-first stores and optimistic updates in real projects.

How do I handle deprecated SolidJS constructs when upgrading to 2.0?▼

Handling deprecated SolidJS constructs when upgrading to 2.0 involves enforcing specific API renames and removing outdated patterns. The patch maps old constructs to new import paths and highlights removals to ensure codebase readiness.

What is the best way to adopt async-first computations in SolidJS?▼

Adopting async-first computations in SolidJS involves understanding microtask batching and split effects introduced in 2.0 beta. The patch explains these mechanisms and provides migration scenarios for updating existing reactive dependencies.

Are there DOM cleanup changes in SolidJS 2.0 migration?▼

Yes, SolidJS 2.0 migration includes DOM cleanup notes alongside boundary migrations and draft-first stores. The patch details how to handle these cleanup operations correctly when upgrading from 1.x to the new reactivity model.