Application show starting screen after some inactivity time

[jeydi243]

Environment

• Operating System: Windows_NT
• Node Version: v22.13.1
• Nuxt Version: 4.0.2
• CLI Version: 3.27.0
• Nitro Version: 2.12.4
• Package Manager: bun@1.2.18
• Builder: -
• User Config: compatibilityDate, devtools, app, modules, colorMode, fonts, css, vite, supabase, runtimeConfig, shadcn, icon
• Runtime Modules: @nuxt/eslint@1.5.2, @nuxt/fonts@0.11.4, @nuxt/icon@1.15.0, @nuxt/image@1.10.0, shadcn-nuxt@2.2.0, @pinia/nuxt@0.11.1, @nuxtjs/supabase@1.5.3, @nuxtjs/color-mode@3.5.2
• Build Modules: -

Reproduction

The error can be reproduced with this repo: https://github.com/jeydi243/sanua

Describe the bug

Hi ! When i run the application the first time it launch correctly but if i just let it for a moment and try to just reload the page it keep showing the loanding page:

javascript console show: 503 (Service Unavailable)

Additional context

No response

Logs

85460161-60f5-45ee-a3fb-d3396c3fb5bd:1  GET http://localhost:3000/clients/85460161-60f5-45ee-a3fb-d3396c3fb5bd 503 (Service Unavailable)

[github-actions]

Would you be able to provide a reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritize it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

Please use a template below to create a minimal reproduction

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

• The Importance of Reproductions
• How to Generate a Minimal, Complete, and Verifiable Example

[cernymatej]

Hi there
The reproduction repository is probably private since I'm getting a 404. Also, was there anything else in the console other than the 503 log? How long was the app idle?

[jeydi243]

Hi @cernymatej , it’s now public. In console the same message of 503. 10 to 15 minutes idle

[josuelrocha]

This is happening to me too. It happens to me when the dev server is inactive for a while, but it also happens "randomly" while I'm actively developing the project. Another thing I noticed is that HMR also doesn't seem to work correctly with certain changes (e.g., one component updates, while another doesn't update). It used to work perfectly.

Here are 2 console outputs from my dev server:

.nuxt/dist directory has been removed. Restarting Nuxt...
ℹ .nuxt/dist directory has been removed. Restarting Nuxt...

✔ Vite client built in 99ms                                                                                                                                     12:23:25 PM
✔ Vite server built in 95ms                                                                                                                                     12:23:25 PM
✔ Nuxt Nitro server built in 937ms                                                                                                                        nitro 12:23:26 PM
ℹ Vite client warmed up in 2ms                                                                                                                                  12:23:26 PM
ℹ nuxt.config.ts updated. Restarting Nuxt...                                                                                                                    12:23:26 PM   
ℹ Vite server warmed up in 10ms                                                                                                                                 12:23:26 PM   
✔ Vite client built in 52ms                                                                                                                                     12:23:27 PM
✔ Vite server built in 53ms                                                                                                                                     12:23:27 PM
✔ Nuxt Nitro server built in 784ms                                                                                                                        nitro 12:23:29 PM
ℹ Vite client warmed up in 1ms                                                                                                                                  12:23:29 PM
ℹ Vite server warmed up in 8ms                                                                                                                                  12:23:29 PM

Whenever I see .nuxt/dist directory has been removed. Restarting Nuxt... or nuxt.config.ts updated. Restarting Nuxt... in the console, I know this problem has occurred and I need to restart the dev server to get it working again.

Note: These messages appear in the console even if these files or folders haven't been touched or changed.

I'm on Windows 11 with Nuxt 4, everything updated to the latest version.
Node v22.15.0

[dan-hale]

@josuelrocha HMR on pages is broken for me, but works fine on components.

Also seeing the crashes after 10-15 minuets.

Possibly a duplicate of nuxt/nuxt#32564?

[josuelrocha]

@dan-hale about HMR, it may be related

[josuelrocha]

Can anyone confirm if this crashing issue is only happening to all Windows users? Because in Nuxt v4.1, in all my projects, my dev server keeps crashing and I have to manually restart it from time to time.