Vercel React View Transitions

vercel-labs/agent-skills/skills/react-view-transitions

作者 vercel-labs1a2c79d4e6c4a2283dc2c614b6538cbe1ed5ca62MIT34K 个星标收录于 2026年11月20日更新于 2026年11月20日仓库今天更新

Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.

精选仅含说明软件开发设计与创意
AI 生成的概览

指导使用 React 原生视图过渡 API 实现页面切换、共享元素、列表重排与 Suspense 显现动画。

功能
提供使用 React 视图过渡 API 为 UI 状态变化添加动画的说明,涉及 组件、addTransitionType 以及 CSS 视图过渡伪元素。内容涵盖动画触发时机(enter、exit、update、share)、按类型区分的方向性导航、共享元素变形、列表标识、Suspense 显现以及 Next.js App Router 集成。还附带 CSS 动画配方、模式、故障排查和减少动态效果等无障碍参考文件。
适用场景
适用于在 React 或 Next.js 应用中添加页面或路由过渡、共享元素动画、进入/退出动画、列表重排动画或前进/后退方向性导航,且不依赖第三方动画库的场景。用户提到视图过渡、startViewTransition、ViewTransition 或过渡类型时也适用。
运行要求
仅为说明文档,不含脚本。非 Next.js 项目需要 React 19.3 或更高版本及 react-dom;Next.js 则使用内置 React canary 的 App Router。目标浏览器需支持视图过渡(Chromium 125+、Firefox 144+、Safari 18.2+),不支持时会优雅降级。

React View Transitions

Animate between UI states using the browser's native document.startViewTransition. Declare what with <ViewTransition>, trigger when with startTransition / useDeferredValue / Suspense, control how with CSS classes. Unsupported browsers skip animations gracefully.

When to Animate

Every <ViewTransition> should communicate a spatial relationship or continuity. If you can't articulate what it communicates, don't add it.

Implement all applicable patterns from this list, in this order:

PriorityPatternWhat it communicates
1Shared element (name)"Same thing — going deeper"
2Suspense reveal"Data loaded"
3List identity (per-item key)"Same items, new arrangement"
4State change (enter/exit)"Something appeared/disappeared"
5Route change (page-level)"Going to a new place"

This is an implementation order, not a "pick one" list. Implement every pattern that fits the app. Only skip a pattern if the app has no use case for it.

Choosing Animation Style

ContextAnimationWhy
Hierarchical navigation (list → detail)Type-keyed nav-forward / nav-backCommunicates spatial depth
Lateral navigation (tab-to-tab)Bare <ViewTransition> (fade) or default="none"No depth to communicate
Suspense revealenter/exit string propsContent arriving
Revalidation / background refreshdefault="none"Silent — no animation needed

Reserve directional slides for hierarchical navigation (list → detail) and ordered sequences (prev/next photo, carousel, paginated results). For ordered sequences, the direction communicates position: "next" slides from right, "previous" from left. Lateral/unordered navigation (tab-to-tab) should not use directional slides — it falsely implies spatial depth.


Availability

  • Next.js: Do not install react@canary — the App Router already bundles React canary internally. ViewTransition works out of the box. npm ls react may show a stable-looking version; this is expected.
  • Without Next.js: Use stable react and react-dom 19.3 or newer (ViewTransition and addTransitionType became stable in React 19.3). Earlier stable React versions do not include these APIs.
  • Browser support: Chromium 125+ (React needs the v2 object form of startViewTransition), Firefox 144+, Safari 18.2+. Graceful degradation on unsupported browsers.

Implementation Workflow

When adding view transitions to an existing app, follow references/implementation.md [blocked] step by step. Start with the audit — do not skip it. Use references/css-recipes.md [blocked] for the applicable CSS and adapt it to the app.


Core Concepts

The <ViewTransition> Component

jsx
import { ViewTransition } from 'react';
<ViewTransition>  <Component /></ViewTransition>

React auto-assigns a unique view-transition-name and calls document.startViewTransition behind the scenes. Never call startViewTransition yourself.

Animation Triggers

TriggerWhen it fires
enter<ViewTransition> first inserted during a Transition
exit<ViewTransition> first removed during a Transition
updateDOM mutations inside a <ViewTransition>, or the boundary itself changing size/position due to an immediate sibling. With nested VTs, mutation applies to the innermost one
shareNamed VT unmounts and another with same name mounts in the same Transition

Only startTransition, useDeferredValue, or Suspense activate VTs. Regular setState does not animate.

Critical Placement Rule

<ViewTransition> only activates enter/exit if it appears before any DOM nodes:

jsx
// Works<ViewTransition enter="auto" exit="auto">  <div>Content</div></ViewTransition>
// Broken — div wraps the VT, suppressing enter/exit<div>  <ViewTransition enter="auto" exit="auto">    <div>Content</div>  </ViewTransition></div>

Styling with View Transition Classes

Props

Values: "auto" (browser cross-fade), "none" (disabled), "class-name" (custom CSS), or { [type]: value } for type-specific animations.

jsx
<ViewTransition default="none" enter="slide-in" exit="slide-out" share="morph" />

If default is "none", all triggers are off unless explicitly listed.

CSS Pseudo-Elements

  • ::view-transition-old(.class) — outgoing snapshot
  • ::view-transition-new(.class) — incoming snapshot
  • ::view-transition-group(.class) — container
  • ::view-transition-image-pair(.class) — old + new pair

See references/css-recipes.md [blocked] for ready-to-use animation recipes.


Transition Types

Tag transitions with addTransitionType so VTs can pick different animations based on context. Call it multiple times to stack types — different VTs in the tree react to different types:

jsx
startTransition(() => {  addTransitionType('nav-forward');  addTransitionType('select-item');  router.push('/detail/1');});

Pass an object to map types to CSS classes. Works on enter, exit, and share:

jsx
<ViewTransition  enter={{ 'nav-forward': 'slide-from-right', 'nav-back': 'slide-from-left', default: 'none' }}  exit={{ 'nav-forward': 'slide-to-left', 'nav-back': 'slide-to-right', default: 'none' }}  share={{ 'nav-forward': 'morph-forward', 'nav-back': 'morph-back', default: 'morph' }}  default="none">  <Page /></ViewTransition>

enter and exit don't have to be symmetric. For example, fade in but slide out directionally:

jsx
<ViewTransition  enter={{ 'nav-forward': 'fade-in', 'nav-back': 'fade-in', default: 'none' }}  exit={{ 'nav-forward': 'nav-forward', 'nav-back': 'nav-back', default: 'none' }}  default="none">

TypeScript: ViewTransitionClassPerType requires a default key in the object.

For apps with multiple pages, extract the type-keyed VT into a reusable wrapper:

jsx
export function DirectionalTransition({ children }: { children: React.ReactNode }) {  return (    <ViewTransition      enter={{ 'nav-forward': 'nav-forward', 'nav-back': 'nav-back', default: 'none' }}      exit={{ 'nav-forward': 'nav-forward', 'nav-back': 'nav-back', default: 'none' }}      default="none"    >      {children}    </ViewTransition>  );}

router.back() and Browser Back Button

router.back() and the browser's back/forward buttons carry no transition types, so type-keyed animations (directional slides) resolve to their default and don't play — untyped shared-element morphs still apply. For typed animations, use router.push() with an explicit URL.

Types and Suspense

Types are available during navigation but not during subsequent Suspense reveals (separate transitions, no type). Use type maps for page-level enter/exit; use simple string props for Suspense reveals.

Shared Element Readiness

A shared element transition can pair elements only when both the old and new views are rendered in the same Transition. If incoming content suspends, only its fallback exists for that update; the resolved content appears in a later Suspense transition and can be animated separately.


Shared Element Transitions

Same name on two VTs — one unmounting, one mounting — creates a shared element morph:

jsx
<ViewTransition name="hero-image">  <img src="/thumb.jpg" onClick={() => startTransition(() => onSelect())} /></ViewTransition>
// On the other view — same name<ViewTransition name="hero-image">  <img src="/full.jpg" /></ViewTransition>
  • Only one VT with a given name can be mounted at a time — use unique names (photo-${id}). Watch for reusable components: if a component with a named VT is rendered in both a modal/popover and a page, both mount simultaneously and break the morph. Either make the name conditional (via a prop) or move the named VT out of the shared component into the specific consumer.
  • share takes precedence over enter/exit. Think through each navigation path: when no matching pair forms (e.g., the target page doesn't have the same name), enter/exit fires instead. Consider whether the element needs a fallback animation for those paths.
  • Two ways a wired-up morph silently never fires: (1) default="none" with no explicit share prop — share resolves to none; (2) type-keyed share where the navigation never adds the type — a plain link click resolves the map's default. Every link that should morph must add the type (transitionTypes on next/link, or addTransitionType).
  • Never use a fade-out exit on pages with shared morphs — use a directional slide instead.

Common Patterns

Enter/Exit

jsx
{show && (  <ViewTransition enter="fade-in" exit="fade-out"><Panel /></ViewTransition>)}

List Reorder

jsx
{items.map(item => (  <ViewTransition key={item.id}><ItemCard item={item} /></ViewTransition>))}

Trigger inside startTransition. Avoid wrapper <div>s between list and VT.

Layout Displacement Morph

Only content inside an activated boundary animates position — everything else teleports to its new layout spot. Wrap the sibling content below a growing/shrinking list in a bare <ViewTransition> so it glides instead of jumping. See Layout Displacement Morph [blocked].

Composing Shared Elements with List Identity

Shared elements and list identity are independent concerns — don't confuse one for the other. When a list item contains a shared element (e.g., an image that morphs into a detail view), use two nested <ViewTransition> boundaries:

jsx
{items.map(item => (  <ViewTransition key={item.id}>                                      {/* list identity */}    <Link href={`/items/${item.id}`}>      <ViewTransition name={`item-image-${item.id}`} share="morph">   {/* shared element */}        <Image src={item.image} />      </ViewTransition>      <p>{item.name}</p>    </Link>  </ViewTransition>))}

The outer VT handles list reorder/enter animations. The inner VT handles the cross-route shared element morph. Missing either layer means that animation silently doesn't happen.

Force Re-Enter with key

jsx
<ViewTransition key={searchParams.toString()} enter="slide-up" default="none">  <ResultsGrid /></ViewTransition>

Caution: If wrapping <Suspense>, changing key remounts the boundary and refetches.

Suspense Fallback to Content

Simple cross-fade:

jsx
<ViewTransition>  <Suspense fallback={<Skeleton />}><Content /></Suspense></ViewTransition>

Directional reveal:

jsx
<Suspense fallback={<ViewTransition exit="slide-down"><Skeleton /></ViewTransition>}>  <ViewTransition enter="slide-up" default="none"><Content /></ViewTransition></Suspense>

For more patterns, see references/patterns.md [blocked].


How Multiple VTs Interact

Every VT matching the trigger fires simultaneously in a single document.startViewTransition. VTs in different transitions (navigation vs later Suspense resolve) don't compete.

Use default="none" Deliberately

Without it, every VT fires the browser cross-fade on every transition — Suspense resolves, useDeferredValue updates, background revalidations. Use default="none" on named/shared elements and type-keyed page VTs.

But it also turns off update (layout/reflow morphs) and share (a named pair with no explicit share prop never morphs). Keyed list items and displaced siblings want update — leave them bare or set update="auto".

Two Patterns Coexist

Pattern A — Directional slides: Type-keyed VT on each page, fires during navigation. Pattern B — Suspense reveals: Simple string props, fires when data loads (no type).

They coexist because they fire at different moments. default="none" on both prevents cross-interference. Always pair enter with exit. Place directional VTs in page components, not layouts.

Nested VT Limitation

When a parent VT mounts/unmounts as one unit with nested VTs inside it, the nested ones do not fire their own enter/exit — only the outermost VT animates. (A child VT mounted inside a persistent parent VT fires enter/exit normally.) Per-item staggered animations during page navigation are not currently available in Next.js; see troubleshooting [blocked] for the upstream experimental status.


Next.js Integration

For Next.js integration (transitionTypes on next/link and useRouter, App Router patterns, Server Components), see references/nextjs.md [blocked].


Accessibility

Always add the reduced motion CSS from references/css-recipes.md [blocked] to your global stylesheet.


Reference Files

  • references/implementation.md [blocked] — Step-by-step implementation workflow.
  • references/patterns.md [blocked] — Patterns, animation timing, and events API.
  • references/troubleshooting.md [blocked] — Symptom-driven debugging and runtime limitations.
  • references/css-recipes.md [blocked] — Ready-to-use CSS animation recipes.
  • references/nextjs.md [blocked] — Next.js App Router patterns and Server Component details.

Full Compiled Document

For the complete guide with all reference files expanded: AGENTS.md

来源与署名

来源:vercel-labs/agent-skills位于skills/react-view-transitions提交1a2c79d

许可证: MIT

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

在 README 中添加徽章

向读者展示该技能已收录于 SourceWeft,徽章链接到本页。

“Listed on SourceWeft”徽章预览
[![Listed on SourceWeft](https://sourceweft.com/badge/skills/gh-vercel-labs-agent-skills-vercel-react-view-transitions.svg)](https://sourceweft.com/skills/gh-vercel-labs-agent-skills-vercel-react-view-transitions?utm_source=readme&utm_medium=badge)

举报或申请下架