Nuxt · NUXT0062
Do not cache personalized handlers without varying
Flags personalized cached handler in Nuxthub project code before it leaks into runtime behavior.
Run this rule
pnpm nuxt doctor --rules nuxthub/no-personalized-cached-handler
Why it matters
Cached server responses are shared beyond one request. Personalized data in a shared cache can leak state or serve stale content.
Recommended fix
Remove personalized cached handler, or move it to the Nuxthub runtime/API that owns that behavior.
Useful links
Example
Avoid personalized cached handlers
Before
export default cachedEventHandler(async (event) => {
const session = await getUserSession(event)
return session.user
})
After
export default defineEventHandler(async (event) => {
const session = await getUserSession(event)
return session.user
})