I came across a problem when trying to set up local-only configuration in a Nuxt application. These local Nuxt config are not simply environment variables, but rather configuration that overrides specific Nuxt settings (like ports, proxies, dev server options) that may not be needed to be included to version control.
The official Nuxt documentation mentions environment-specific overrides using $development and $production keys, but these are still within the committed nuxt.config.ts file.
https://nuxt.com/docs/4.x/getting-started/configuration#environment-overrides
However, this doesn't solve the problem of having local-only configuration, we could import a config file that is gitignored and put it on per-environment overrides, but if we do that, it would fail in CI/CD pipelines where the file doesn't exist and it's not even necessary to have it there just make the build work on CI/CD. (I hope that makes sense)