Nuxt 3 Server Routes with Nitro: Co-located Private API Architecture
Design pattern for Nuxt 3 server routes with Nitro, covering trust boundaries, runtimeConfig separation, operational checks, and when to scale beyond co-location.
Loading…
ReadMeFeed / Community knowledge
#runtime-config
Real questions. Useful conversations. Find the people who know your stack.
Deploying Nuxt 3 with Nitro on Serverless Platforms: Architecture, Checks, and Failure Modes
Learn how to turn a Nuxt 3 app into a single Nitro‑powered serverless function, the minimal design, trust boundaries, operational checks, and when to re‑architect.
nuxtHandling Secrets and Proxies with Nuxt 3 Server Routes
Stop leaking API keys in your frontend. Learn how to use Nuxt 3 server routes and Nitro to create secure proxies and manage private runtime configurations.
Configuring Conditional Debug Logging in Elm with Runtime Flags
Goal Design a helper around Elm's Debug.log that only emits messages when a runtime flag is enabled, allowing developers to retain useful alerts during development while suppressing noise in other contexts. Constraints and uncertainties The Debug.log function is removed by the Elm optimizer in production builds, so any wrapper that assumes logging will alway
Does a library’s configuration need to be declared as runtime to work correctly in a production release?
When developing an Elixir application with Mix, configuration files in config/ are loaded on each start, so changes to config/prod.exs take effect immediately. In a production release built with mix release or Distillery, static configuration is compiled into sys.config ; only values wrapped in {:system, "VAR"} or placed in config/runtime.exs are read from t
Migrating to Nuxt 3 runtimeConfig: which keys silently become public?
Context While migrating a Nuxt 2 application (which used publicRuntimeConfig and privateRuntimeConfig ) to Nuxt 3's unified runtimeConfig , I need to guarantee that no secret values accidentally cross into the client bundle. My understanding is that only keys under runtimeConfig.public are serialized to the browser, while top-level keys stay server-only. Con
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