nuxt/no-module-scope-state

Dlaczego

A module is loaded once per server process and shared by every request it serves. export const user = ref(null) in a composable file therefore holds the last visitor's data for the next one: one user can see another user's name, cart or token in server-rendered HTML, and the value never gets freed.

Poprawka

Create state inside a function that runs per request: export const useUser = () => useState('user', () => null), or a Pinia store (defineStore), which Nuxt creates per request. A plain <script> block of a .vue file is module scope too; <script setup> is per component. Client-only files (*.client.ts plugins) may keep module state.

Przykłady

// bad (composables/user.js)
export const user = ref(null)
// good
export const useUser = () => useState('user', () => null)

Źródła

• Nuxt docs, State Management (never define const state = ref() outside setup)
• Vue docs, Server-Side Rendering (cross-request state pollution)

Przeczytaj w terminalu

npx github:dawidolko/frontend-skills explain nuxt/no-module-scope-state