-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nuxt extremely slow on dev startup #26211
Comments
Try to add
to your tsconfig.json |
Is there any update on this issue? I have this problem the exact same way. Every time I reload my webpage I have to wait almost 40 to 60 seconds, sometimes even longer. Information about project:
If you feel like you would need more information, please reach out. |
At first, I thought it has something to do with node_modules. But after some researches, it's all about nuxt/ui, Remove nuxt/ui, because it renders all tailwind css, There is over 600 kb of tailwind.css. And sometimes it renders tailwind.css twice. Shadcn only renders tailwindcss over 100kb. Another solution is to change your config in nuxt.config.ts Change to |
I haven't used nuxt/ui in my project, I am using vuetify as a UI library. { |
What is your config? With just your package.json, it's very fast... |
Here is my nuxt.config.ts: import vuetify, { transformAssetUrls } from "vite-plugin-vuetify"; export default defineNuxtConfig({ |
The problem is that I have the same issue while creating a brand new project on a entirely different system, it also doesn't seem to matter whether I am on MacOS or Windows, the issue still persists. |
For anyone else having this issue, please check any program/script etc that checks files being transmitted over internet. This issue presented itself to me after I updated my Bitdefender. Due to this update, the node_modules directory wasn't excluded anymore in the files being scanned. This caused the enormous long loading times. Disabling Bitdefender or excluding all node_modules solved this issue for me. |
Don't use localhost, use 127.0.0.1 |
On nuxt My current project info (not experiencing this issue): ------------------------------
- Operating System: Windows_NT
- Node Version: v20.11.1
- Nuxt Version: 3.9.3
- CLI Version: 3.12.0
- Nitro Version: 2.9.6
- Package Manager: npm@10.8.1
- Builder: -
- User Config: extends, nitro, modules, sanity, gtag, runtimeConfig, site, routeRules
- Runtime Modules: @pinia/nuxt@0.5.1, nuxt-gtag@2.0.6
- Build Modules: -
------------------------------ EDIT: I'm using the Vuetify Nuxt module: https://github.com/userquin/vuetify-nuxt-module |
@besscroft are you using WSL? I had a similar problem with WSL2 and the filesystem. I've fixed the problem by moving files inside Linux. It was one of the solutions from here. |
Have same problem, startup time > 7 minutes
npm run dev (debug = true):
after |
To follow up on this, my build times have significantly improved since v3.12.4. Thank you @danielroe! Updating my layers to that version also helped. It's still slightly slower once I add in the EDIT: Meant to post this on the related issue here: #27106 (comment) |
@lingjhf wow, using 127.0.0.1 instead of localhost did the trick for me, loading time in dev mode went from 2 minutes to 3 seconds 🤯🤯🤯 |
I think we need to differentiate between several issues that are discussed in this thread, I don't think they are caused by the same problem, so: Issue 1: Slow initial build time in dev Issue 2: Slow browser-level project initialization |
For anyone experiencing slow dev server in projects utilizing Nuxt Layers, check out #30137 |
Environment
Nuxt project info: 12:44:36
Reproduction
https://github.com/besscroft/kamera
Describe the bug
pnpm run dev

Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: