solidjs/solid

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.