Server-Side Runtime Config Access vs Client-Side Hydration in Nuxt
The goal is to make a configuration value defined in a .env file available both during server-side rendering and client-side hydration after a production build. In development, Nuxt injects process.env into both server and client bundles, so direct access works. In production builds, only variables exposed via publicRuntimeConfig are sent to the client; dire
nuxt