nuxt/no-browser-api-in-setup

Dlaczego

With server rendering, <script setup> runs first on the server, where window, document and localStorage do not exist: the page answers with a 500 error, or, when the access is guarded badly, the server and browser render different HTML and hydration throws the server's markup away.

Poprawka

Read browser state after mounting (onMounted(() => { theme.value = localStorage.getItem('theme') })), guard with if (import.meta.client), use a cookie that both sides can read (useCookie('theme')), or render the part only in the browser (<ClientOnly> or a *.client.vue component).

Przykłady

// bad
const theme = ref(localStorage.getItem('theme') ?? 'light')
// good
const theme = useCookie('theme', { default: () => 'light' })

Źródła

• Nuxt docs, Hydration best practices (browser-only APIs in server context)
• Vue docs, Server-Side Rendering (access to platform-specific APIs)

Przeczytaj w terminalu

npx github:dawidolko/frontend-skills explain nuxt/no-browser-api-in-setup