runtimeConfig will not be updated after "yarn build"

Environment

• Operating System: Darwin
• Node Version: v16.17.0
• Nuxt Version: 3.0.0-rc.8
• Package Manager: yarn@1.22.10
• Builder: vite
• User Config: typescript, head, runtimeConfig, modules, css, styleResources, plugins, components, experimental, vite, hooks
• Runtime Modules: @nuxtjs/tailwindcss@5.3.2
• Build Modules: -

Reproduction

1. Create a .env file at the project’s root dir.
2. Follow the instruction to use the runtimeConfig.
3. yarn build to build the artifacts.
4. yarn start to see the current NUXT_ABC value.
5. Stop or kill the process
6. Change the value of NUXT_ABC you have set by source .env or NUXT_ABC=123 directly.
7. yarn start again and you will see the value hasn’t been changed.

Describe the bug

runtimeConfig does not behave as I expected as a “runtime” config. The configs were set after yarn build. And you can not change them via any solutions since they were already determined in .output/server/chunks/nitro/node-server.mjs.

Additional context

I want to use the same container image and apply the env configs for every environment by using ‘yarn build’ and yarn start. Or I can only use yarn dev and customize the other settings for achieving the goal?

Logs

No response

[andretw]

@danielroe Thank you, I didn’t realize that there is a convention between them. Thanks a lot!

[danielroe]

@andretw It should be NUXT_PUBLIC_MY_ABC in your case. Also note that you need to have a fallback value or have the variable defined when you build the app.