sveltejs/svelte

Choose this fork only if you want a deeply modified Svelte codebase and are prepared to maintain it yourself. For most adopters, upstream Svelte is the safer choice because this fork is stale and materially diverged, so it is more likely to miss recent fixes and require significant reconciliation work.

Prefer this fork only if you specifically need its early runes/compiler behavior or want to build on its custom SSR/migration changes. For most adopters, upstream Svelte is the better choice because this fork is stale and far behind current fixes and tooling.

Choose this fork only if you specifically want a frozen, older Svelte 4-derived codebase. If you want current framework behavior, fixes, and compatibility, upstream is the safer choice.

Choose this fork only if you specifically need the older Svelte 3.38.3-era codebase; otherwise upstream is the better default because this fork is stale and significantly behind.

Prefer this fork only if you need a heavily customized Svelte codebase and are willing to absorb merge and regression risk. If you want current upstream behavior and active maintenance, stay on upstream instead.

Prefer this fork only if you want a historically diverged Svelte internals branch and are prepared to maintain it yourself. For most adopters, upstream is the better choice because this fork is stale and far from current fixes and APIs.

Choose this fork only if you specifically need its older, customized Svelte snapshot. For most adopters, upstream Svelte is the better default because this fork is stale and far behind current framework work.

Adopt this only if you specifically need the exact merge-base snapshot. For most users, upstream is the better choice because this fork adds nothing and is already behind on recent fixes.

Prefer this fork only if you want a customized Svelte runtime/compiler and can absorb significant divergence from upstream. For most adopters who want stability, documentation continuity, and easy upgrades, upstream is the safer choice.

Prefer this fork only if you need its custom compiler direction or historical snapshot and are prepared to maintain it yourself. If you want current Svelte with active bug fixes, docs, and tooling, upstream is the safer choice.

Choose this fork only if you want a long-lived experimental Svelte variant and are prepared to own the merge debt. If you mainly want a current, low-risk Svelte base, upstream is the better choice.

Prefer this fork only if you specifically need its migration-focused changes or custom compiler behavior. For most adopters, upstream Svelte is the safer choice because this fork is stale and likely missing many recent fixes and docs.

Prefer this fork only if you specifically want a customized, experimental Svelte base and can own long-term maintenance. If you want a current, low-risk Svelte distribution, upstream is the better choice.

Choose this fork if you want a materially customized Svelte internals branch and can tolerate merge debt. Choose upstream if you want the latest fixes, compatibility, and lower maintenance risk.

Prefer this fork only if its added media-query/form-default behavior or internal experiments are the goal. For general Svelte adoption, upstream is the safer choice because this fork is stale and materially behind current fixes.

Prefer this fork only if you need its custom compiler/runtime/migration changes and are willing to own the maintenance burden. For most adopters who want current Svelte with low risk, upstream is the better choice.

Choose this fork if Spanish localization is the priority. Choose upstream if you need current Svelte fixes, active maintenance, and the latest tooling/docs.

Choose this fork only if you want a heavily altered, stale Svelte base for internal experimentation or long-term custom maintenance. If you want current Svelte behavior, ecosystem compatibility, or low adoption risk, upstream is the better choice.

Choose this fork only if you want fork-specific compiler experimentation or already depend on its custom behavior. If you want current Svelte, stable typings, migration help, and low-risk upgrades, upstream is the safer choice.