finds.dev

shuding/next-view-transitions

Use CSS View Transitions API in Next.js App Router.

View on GitHubHomepage ↗

★ 2,385TypeScriptMITupdated Mar 2026

// the take

A thin wrapper that wires the browser's View Transitions API into Next.js App Router navigation. You drop in a provider and swap `next/link` for the library's `Link` — page transitions animate without you writing any animation code. Aimed at simple sites and portfolios.

The implementation is tiny (6 source files), which means it's auditable and won't bloat your bundle. The hook-based escape hatch (`useTransitionRouter`) covers programmatic navigation so you're not locked into the `Link` component. The author (Shu Ding, Vercel) knows the Next.js internals deeply, so the App Router integration is not naive. Works today without waiting for React/Next.js to ship first-party support.

The disclaimer is the most important part of the README: concurrent rendering, Suspense, and streaming are explicitly unsupported — if your app uses any of these, transitions will break in subtle ways. Browser support still requires a polyfill for Firefox and Safari unless you're fine with no-transition fallback. The library appears to be in maintenance mode (last commit March 2026, few issues addressed), which is a problem since Next.js App Router evolves fast. Zero customization API for controlling which elements participate in the transition — you're stuck with full-page swaps unless you write CSS yourself.

We read the README, the directory tree and a key source file in June 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
2,385
Forks
92
Language
TypeScript
License
MIT
Last commit
6 Mar 2026

// nearby

If next-view-transitions isn't quite it.

All repos →