slidevjs/slidev

Prefer this fork only if you specifically want its VS Code and workflow customizations and are willing to maintain a significant divergence from upstream. If you want the newest Slidev features, fixes, and docs with lower operational risk, upstream is the safer default.

Prefer this fork only if its local presenter/export/editor changes match your needs and you are willing to own a stale, highly divergent codebase. If you want current Slidev features, compatibility, and lower maintenance risk, upstream is the better default.

Prefer upstream unless you specifically need this fork's older custom behavior. The fork is materially behind and stale, so it is a poor default choice for new adoption but may still fit legacy/internal deployments that need its local workflow changes.

Choose upstream unless you specifically need this fork’s older customized behavior. This fork is materially behind, stale, and likely missing several current Slidev capabilities; it only makes sense if you want a frozen beta baseline or a fork you plan to own end-to-end.

Prefer upstream unless you specifically need this fork’s custom behavior. Choose the fork only if its local changes are the product, because it is materially behind and structurally divergent from current Slidev.

Choose upstream unless you specifically need this exact fork as a starting point. It adds no clear new capabilities, and it is substantially behind on upstream maintenance.

Prefer upstream unless you need this exact fork snapshot; it adds no evident capabilities and is materially behind current Slidev.

Prefer upstream unless you specifically need this exact older snapshot; this fork adds no visible product value and mainly carries the cost of being behind.

Prefer this fork only if you need its specific internal customizations. For general Slidev use, upstream is the better choice because this fork is stale, substantially diverged, and appears to have removed or lagged on user-facing workflows like export and documentation.