Avoid multiple loading of nuxt.config in dev mode

[AndrewBogdanovTSS]

Environment

---

• Operating System: Linux
• Node Version: v18.18.0
• Nuxt Version: 3.8.1
• CLI Version: 3.9.1
• Nitro Version: 2.7.2
• Package Manager: npm@9.4.2
• Builder: -
• User Config: devtools
• Runtime Modules: -
• Build Modules: -

---

Reproduction

https://stackblitz.com/edit/github-orzeps?file=nuxt.config.ts

Describe the bug

nuxt.config.ts file is executed 2 times in dev mode instead of 1, this can lead to performance issues and suboptimal in general.

Additional context

Logs

❯ npm run dev

> dev
> HOST=0.0.0.0 nuxt dev

Nuxt 3.8.1 with Nitro 2.7.2                                                                                    11:32:26 AM
EXECUTING NUXT CONFIG                                                                                          11:32:26 AM
                                                                                                              
  ➜ Network:  https://stackblitz.com/edit/kkvigobwa.github [QR code]
  ➜ Local:    http://0.0.0.0:3000/
  ➜ Network:  http://192.168.1.104:3000/

EXECUTING NUXT CONFIG                                                                                          11:32:31 AM
ℹ Compiled plugins/server.mjs in 1085.13ms                                                                    11:32:32 AM
ℹ Compiled plugins/client.mjs in 1312.03ms                                                                    11:32:32 AM
ℹ Vite client warmed up in 265ms                                                                              11:32:36 AM
ℹ Vite server warmed up in 1331ms                                                                             11:32:37 AM
✔ Nitro built in 756 ms

[bolt-new-by-stackblitz]

Start a new pull request in StackBlitz Codeflow.

• github-orzeps (Open reproduction)
• kkvigobwa (Open reproduction)

[pi0]

This is a requirement of loading nuxt config once to predict server configuration.

I'm not sure if there would be an easy way to avoid it but also should not affect performance as jiti hard caches config and all dependencies on first load.

It would be best if you avoid any top level logic in nuxt config that can cause slowing down development mode and instead use hooks.

(keeping open to think more if any way we can at least reduce it's overhead, even small)