Skip to main content
← 返回博客
next.jsreact-19dark-modezustandperformance

Next.js 暗色模式：无闪烁、无 React 19 警告

如何用 Zustand + useServerInsertedHTML 替换 next-themes，在 Next.js 15+ 中实现无闪烁暗色模式。

发布于 2026年4月11日8 分钟阅读

TL;DR

next-themes 在 React Client Component 内渲染一个 <script> 标签以防止主题闪烁（FOUC）。React 19 会对此发出警告——且无法抑制。该库自 2025 年 3 月起未再更新。解决方案：用 Zustand store + useServerInsertedHTML 替换 next-themes，在 React 树外注入脚本。零新增依赖。零 FOUC。零警告。

问题所在

如果你在 Next.js 15+ 和 React 19 中使用 next-themes，每次页面加载时控制台都会出现以下错误：

Encountered a script tag while rendering React component.
Scripts inside React components are never executed when rendering on the client.
Consider using template tag instead.

src/providers/theme-provider.tsx (7:10) @ ThemeProvider

这不是水合不匹配问题。React 19 明确警告：由 React 组件在客户端渲染的 <script> 标签永远不会执行。脚本在 SSR 期间有效（它存在于 HTML 中），但 React 将其标记为不正确。

原因分析

next-themes 需要在 React 水合之前在 <html> 上设置正确的主题类——否则会出现错误主题的闪烁。为此，它通过 React.createElement 注入内联 <script>：

next-themes internals (minified)
// next-themes renders a <script> inside a Client Component
return React.createElement(Provider, { value },
  React.createElement("script", {
    suppressHydrationWarning: true,
    dangerouslySetInnerHTML: { __html: `(...theme init code...)` }
  }),
  children
)

React 19 改变了行为：组件内的 script 标签现在会被明确标记。在 React 19 之前，这被默默忽略。脚本上的 suppressHydrationWarning 属性无效——它抑制的是水合警告，而非"组件内 script"警告。

我们尝试过的方案（以及失败原因）

我们系统地尝试了每一种方法：

AttemptResult
suppressHydrationWarning on <html>Suppresses hydration mismatch, but NOT the script tag warning
Delay mount with useState + useEffectWarning disappears, but causes FOUC (theme flash)
Raw <script> in layout <head>React 19 catches it — same warning even in Server Components
next/script with beforeInteractiveStill rendered inside React tree — same warning
Remove <head>, put Script in bodySame warning — it's inside <html> which is React-managed
next-themes@1.0.0-beta.0Beta, no release date, unclear if fixed

解决方案：Zustand + useServerInsertedHTML

关键洞察：useServerInsertedHTML 是 Next.js 的一个 hook，它将 HTML 注入 SSR 流中——在 React 组件树之外。脚本存在于 HTML 中，但 React 在客户端渲染时永远"看不到"它——因此没有警告。结合 Zustand store 实现响应式主题状态，我们得到了一个完整的替代方案，零新增依赖。

工作原理

SSR (server):
  useServerInsertedHTML → injects <script> into HTML stream
  ↓
  Browser receives HTML with theme script already in it
  ↓
  Script runs BEFORE React hydrates → correct class on <html>
  ↓
  No flash. No mismatch. No warning.

Client (after hydration):
  useEffect → _init() → Zustand store syncs with localStorage
  ↓
  useTheme() → reactive theme state for components

第一步：Zustand Store

Store 管理主题状态、DOM 类应用、系统主题检测和跨标签页同步。_init() 方法返回一个供 useEffect 使用的清理函数：

store/use-theme-store.ts
import { create } from "zustand";

const STORAGE_KEY = "theme";
const MEDIA_QUERY = "(prefers-color-scheme: dark)";

function getSystemTheme(): "light" | "dark" {
  return window.matchMedia(MEDIA_QUERY).matches ? "dark" : "light";
}

function applyTheme(resolved: string, disableTransition: boolean) {
  const d = document.documentElement;

  if (disableTransition) {
    const style = document.createElement("style");
    style.appendChild(
      document.createTextNode(
        "*,*::before,*::after{transition:none!important}"
      )
    );
    document.head.appendChild(style);
    window.getComputedStyle(document.body);
    setTimeout(() => document.head.removeChild(style), 1);
  }

  d.classList.remove("light", "dark");
  d.classList.add(resolved);
  d.style.colorScheme = resolved;
}

interface ThemeState {
  theme: string;
  systemTheme: "light" | "dark";
  resolvedTheme: string;
  setTheme: (theme: string) => void;
  _init: (disableTransition: boolean) => () => void;
}

export const useThemeStore = create<ThemeState>((set, get) => ({
  theme: "system",
  systemTheme: "light",
  resolvedTheme: "light",

  setTheme: (newTheme) => {
    const { systemTheme, disableTransitionOnChange } = get();
    const resolved = newTheme === "system" ? systemTheme : newTheme;
    localStorage.setItem(STORAGE_KEY, newTheme);
    applyTheme(resolved, disableTransitionOnChange);
    set({ theme: newTheme, resolvedTheme: resolved });
  },

  _init: (disableTransition) => {
    const stored = localStorage.getItem(STORAGE_KEY) || "system";
    const system = getSystemTheme();
    const resolved = stored === "system" ? system : stored;

    set({ theme: stored, systemTheme: system, resolvedTheme: resolved });
    applyTheme(resolved, disableTransition);

    // System theme changes
    const mq = window.matchMedia(MEDIA_QUERY);
    const onChange = (e: MediaQueryListEvent) => {
      const newSystem = e.matches ? "dark" : "light";
      const { theme } = get();
      set({ systemTheme: newSystem,
            resolvedTheme: theme === "system" ? newSystem : theme });
      if (theme === "system") applyTheme(newSystem, disableTransition);
    };
    mq.addEventListener("change", onChange);

    // Cross-tab sync
    const onStorage = (e: StorageEvent) => {
      if (e.key !== STORAGE_KEY || !e.newValue) return;
      const system = getSystemTheme();
      const resolved = e.newValue === "system" ? system : e.newValue;
      set({ theme: e.newValue, resolvedTheme: resolved });
      applyTheme(resolved, disableTransition);
    };
    window.addEventListener("storage", onStorage);

    return () => {
      mq.removeEventListener("change", onChange);
      window.removeEventListener("storage", onStorage);
    };
  },
}));

export function useTheme() {
  return useThemeStore((s) => ({
    theme: s.theme,
    setTheme: s.setTheme,
    resolvedTheme: s.resolvedTheme,
    systemTheme: s.systemTheme,
  }));
}

第二步：ThemeProvider

Provider 做两件事：通过 useServerInsertedHTML 注入防止 FOUC 的脚本，并在挂载时初始化 Zustand store：

providers/theme-provider.tsx
"use client"

import { useEffect } from "react"
import { useServerInsertedHTML } from "next/navigation"
import { useThemeStore } from "@/store/use-theme-store"

const THEME_INIT_SCRIPT = `(function(){
  try {
    var t = localStorage.getItem("theme") || "system";
    var r = t;
    if (t === "system") {
      r = window.matchMedia("(prefers-color-scheme: dark)").matches
        ? "dark" : "light";
    }
    document.documentElement.classList.remove("light", "dark");
    document.documentElement.classList.add(r);
    document.documentElement.style.colorScheme = r;
  } catch(e) {}
})()`

export function ThemeProvider({
  children,
  disableTransitionOnChange = false,
}) {
  // Injects script into SSR HTML outside the React tree
  // — prevents FOUC without triggering React 19 warning
  useServerInsertedHTML(() => (
    <script dangerouslySetInnerHTML={{ __html: THEME_INIT_SCRIPT }} />
  ))

  useEffect(() => {
    return useThemeStore.getState()._init(disableTransitionOnChange)
  }, [disableTransitionOnChange])

  return <>{children}</>
}

第三步：Layout

app/layout.tsx
import { ThemeProvider } from "@/providers/theme-provider"

export default function RootLayout({ children }) {
  return (
    <html lang="en" suppressHydrationWarning>
      <body>
        <ThemeProvider disableTransitionOnChange>
          {children}
        </ThemeProvider>
      </body>
    </html>
  )
}

第四步：使用

components/theme-switch.tsx
import { useTheme } from "@/store/use-theme-store"

export function ThemeSwitch() {
  const { theme, setTheme } = useTheme();

  return (
    <button onClick={() => setTheme(
      theme === "dark" ? "light" : "dark"
    )}>
      {theme === "dark" ? "☀️" : "🌙"}
    </button>
  );
}

从 next-themes 迁移

API 设计为完全兼容。每个文件只需更改一处导入即可完成迁移：

migration
- import { useTheme } from "next-themes"
+ import { useTheme } from "@/store/use-theme-store"

  // API is identical — no other changes needed
  const { theme, setTheme, resolvedTheme, systemTheme } = useTheme()

对比

next-themesZustand + useServerInsertedHTML
React 19 warningYes — <script> in client componentNo
FOUC preventionYesYes
Cross-tab syncYesYes
System theme detectionYesYes
disableTransitionOnChangeYesYes
Bundle size~3.5 KB~1.5 KB (uses existing Zustand)
Dependencies+1 (next-themes)0 (Zustand already in project)
Maintenance riskAbandoned since March 2025Your own code

为什么不用其他替代方案？

@wrksz/themes

同样使用 useServerInsertedHTML 的即插即用替代品。可以使用，但又是一个单一维护者的依赖项。如果 next-themes 教会了我们什么——依赖项会被遗弃。用 ~100 行代码，你可以完全掌控解决方案。

next-themes@1.0.0-beta.0

已发布到 npm，但没有发布日期，没有更新日志，不清楚 React 19 警告是否已修复。不值得用生产代码去赌一个无限期的 beta 版本。

纯 CSS (prefers-color-scheme)

适用于系统主题检测，但无法处理用户偏好持久化（localStorage）、手动主题切换或"system"选项。这些需要 JavaScript。

结论

  1. next-themes 实际上已被放弃——最后一次发布是 2025 年 3 月，React 19 警告未修复
  2. useServerInsertedHTML 是 Next.js 中无需 React 警告进行脚本注入的正确原语
  3. Zustand 以比 Context provider 更少的代码提供响应式主题状态
  4. 整个解决方案约 100 行，零新增依赖，每一行都由你掌控

参考资料

← 返回博客