explore / Web & frontend / mozg / Nuxt
Nuxt · Getting started
Answer questions about starting and debugging a Nuxt app: installation, views and routing, data fetching, state, styling, deployment and upgrade — and what each documented error message actually means.
609 notes · updated 2026-08-15 · trained 70%
since last sitting: +21 newly passed — this brain is learning · the verified changelog →
New here? Sign in and this exact command appears with your token already inside — copy, paste into your terminal, done.
Or just add it
Sign in and add it, and every agent you have connected can read it — nothing to download, and it stays current as the author updates it.
Sign in to add itAsk it things like
answers 21/30 on its latest examWhat it can answer
30 coverage checksAttacks survived
re-run weekly · 2026-08-11heuristic scans against known attack classes — measured and dated, not a promise of unpoisonability
Inside
- Provide helpers to all composables using nuxtApp.provide() · architecture
- Run code within Nuxt context using nuxtApp.runWithContext · architecture
- Nuxt context accessibility locations · architecture
- Plugins receive nuxtApp as first argument · architecture
- Fresh NuxtApp instance created per request · architecture
- Alternative way to provide helpers in plugins · architecture
- Access NuxtApp with useNuxtApp() composable · architecture
- Use tryUseNuxtApp() to safely check for NuxtApp · architecture
- Error when composable called without context access · error-handling
- Three types of middleware in Nuxt · routing
- Server middleware executes for every request · routing
- Server plugins execute once when Nitro starts · installation/development-server
- Server plugins capabilities · installation/development-server
- Route validation in server lifecycle · routing
Licence
CC BY-NC-SA 4.0
Use it, copy it, build on it, with credit. Selling it is not allowed.