Discofork
Repository brief

solidjs/solid

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-31T09:47:41.507Z
1mo ago

solidjs/solid

SolidJS/solid is an actively maintained, high-traffic JavaScript UI library focused on declarative UI with fine-grained reactivity and real-DOM updates instead of a virtual DOM. It has strong ecosystem signals, with 35,354 stars and 1,056 forks, and recent commits through 2026-03-30. Forks are most likely interesting if you care about reactive UI runtime/compiler internals, TypeScript-based library work, or contributing to a mature OSS frontend core.

GitHub
Loading tags...
Stars35,354
Forks1,056
Default branchmain
Last pushed2026-03-30T22:11:31Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Use this fork only if you want an almost-unmodified SolidJS snapshot. If you want the latest fixes and release updates, upstream is the better choice.

Choose this fork only if you need its custom runtime/SSR/element changes and are prepared to own the merge burden. If you want the most current SolidJS behavior, upstream is the safer default.

Prefer upstream unless you specifically need the fork’s older runtime/type fixes and are willing to own a large rebase gap. This fork is best for legacy maintenance or targeted experimentation, not for new projects or low-risk adoption.

Prefer this fork only if you need its specific runtime/typing/SSR experiments and are prepared to maintain a large divergence. For most adopters, current upstream is the safer choice because this fork is materially stale and likely missing many later fixes.

Choose this fork only if you need its older, customized Solid baseline or its SSR/element/Babel-specific changes. If you want current SolidJS behavior, active fixes, and lower maintenance risk, upstream is the better default.

Prefer upstream unless you specifically need this fork's older internal behavior or custom solid-element/SSR/tooling changes. For most adopters, the fork is too stale and too far behind to be a good default.

Do not adopt this as a general-purpose SolidJS base unless you specifically need the 2020-era fork behavior. For most users, upstream is clearly the better choice because this fork is stale, heavily diverged, and likely missing years of fixes and tooling improvements.

Prefer this fork only if you need the `resolveChildren` overflow fix immediately; otherwise upstream is the safer default because it is much more current and actively maintained.

Prefer upstream unless you specifically want this near-identical fork for local pinning or minor repo housekeeping. It does not appear to add meaningful capabilities, and it is already behind upstream on recent fixes.

Choose upstream unless you specifically need this exact snapshot; the fork adds no visible capabilities and mainly carries upstream lag.

solidjs/solid · Discofork