Similar issues - #30605 - nuxt/nuxt - unsight.dev

# Use custom runtime environmental variables (instead of NUXT_ prefix)

Use custom runtime environmental variables (instead of NUXT_ prefix)

nuxt/nuxt · updated1 year ago · 34% similar

documentationdiscussionworkaround availablenitro

Devops: Ops should be able to configure nuxt as easily as Dev. 'nuxt dev' works but 'nuxt build' doesn't. process.env.SOME_LIB_VAR

nuxt/nuxt · updated8 months ago · 33% similar

pending triagedxnitro

[ENV] Runtime variables actually configurable at runtime

nuxt/nuxt · closed3 years ago · 38% similar

enhancement2.x

NUXT_PUBLIC_XXX environment variables not overriding public runtimeConfig in production

nuxt/nuxt · closed2 years ago · 36% similar

3.xpending triage

RuntimeConfig does not display proper environment variable hint when already using UPPER_SNAKE_CASE

nuxt/nuxt · closed2 years ago · 35% similar

good first issuetypes3.xdxbug

Using runtime config in the nuxt.config.js

nuxt/nuxt · closed3 years ago · 35% similar

enhancement2.x

Environment variables not synced from `.env` file on production build.

nuxt/nuxt · closed3 years ago · 35% similar

3.xpending triage

Using runtime config in nuxt.config.js

nuxt/nuxt · closed3 years ago · 34% similar

enhancement2.x

Enivornment variables in runtimeConfig not being set at runtime (Nuxt rc.8)

nuxt/nuxt · closed3 years ago · 34% similar

documentation3.x

[Nuxt 3.1.1] Defining `runtimeConfig.public.myValue = ''` is not injected with `.env` at runtime of a module

nuxt/nuxt · closed3 years ago · 34% similar

3.xpending triage