ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When building a Nuxt 3 site, developers often face the decision between Server‑Side Rendering (SSR) and Static Site Generation (SSG). SSR renders each request on the server, enabling real‑time, personalized data at the cost of per‑request latency. SSG pre‑builds pages at deploy time, delivering CDN‑cached responses that are lightning‑fast but require a rebui
A Nuxt 3 (v3.4+) app builds cleanly with nuxt build , but the deployed server exits during startup with an error resembling Cannot find module '@/utils/config' . The build log shows no warning, so the failure only surfaces when Nitro actually runs the server bundle. The suspicion is that @/ aliases are resolved for client-side code by Vite, while server-side
A Nuxt 3 app needs to surface failures usefully without turning every problem into a full-screen interruption. The framework ships no notification system, so the nearest documented lever is error handling: showError or createError with fatal: true renders the app-wide error.vue page, while non-fatal errors are left for local handling, and useAsyncData and us
In a Nuxt 3 SSR application, I need to decide how to fetch data that changes frequently on the backend. Both useFetch and useAsyncData hydrate server results into the payload to avoid double-fetching, but I am unsure which approach gives more predictable control when cached results risk becoming stale. My understanding is that useFetch is a wrapper around us
Global Log Level Behavior Nuxt 3 provides a log.level configuration in nuxt.config.ts to manage console verbosity. By setting this to 'error' or 'fatal' , developers can suppress info and warn messages to reduce noise during the build and development cycles. Internal Module Consistency While the global configuration affects the core framework and server midd
Nuxt 3 maps files under server/api to Nitro routes, such as server/api/items.get.ts becoming /api/items. Handlers receive an H3 event object and run in the server-only runtime, so application authentication state from client-side plugins is not automatically available. The goal is to apply one authorization check to every server/api endpoint instead of repea
When running a Nuxt 2 application under Nuxt Bridge, developers can gradually introduce Nuxt 3 features such as composables and server APIs on a per‑route basis. The bridge allows both webpack‑based Nuxt 2 pages and Vite‑powered Nuxt 3 pages to coexist, but the documentation does not clarify how the server‑side rendering cache treats requests that originate
Goal: Ensure that data fetching in Nuxt 3 handles both navigation‑initiated cancellation and request timeouts uniformly, especially during server‑side rendering where no client‑side AbortSignal is available. Currently, useFetch automatically forwards an AbortSignal when the navigating component is destroyed, but it does not apply a default timeout; during SS
nuxt
nuxtjs