-
Notifications
You must be signed in to change notification settings - Fork 65
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
Slow initial loading & slow refresh in Nuxt 3.7.1 (dev only) #171
Comments
luke-z
changed the title
Slow initial loading & slow refresh in Nuxt 3.7.1 (mostly likely affecting WSL?)
Slow initial loading & slow refresh in Nuxt 3.7.1 (dev only)
Sep 11, 2023
dup #118 |
Oh, didn't think about checking the cli issues, sorry 😅 |
Closing in favor of #118 |
@pi0 Awesome, thanks for all of the work you and the team do btw! I'll make sure to upgrade to the new version asap and report back in case there should be any problems :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Reproduction
npx nuxi@latest init my-app
and choose yarn as the package manager. (just for fun I also tried it with bun, same problem)yarn dev
.Describe the bug
I have experienced this on two projects when I upgraded them to v3.7.1.
One was on v3.4.1 today before upgrading, the other on v3.6.5.
I experienced it on two separate systems running a similar config (both Win11, node 18, yarn) in WSL.
Both of the browsers (Edge and Brave) I tested it in loaded the page extremely slow, which can also be seen in the browsers dev tools network tab (see attached pic).
I also tried removing the new Nuxt devtools package which is now being shipped with Nuxt, but that made no difference.
The only way it can be resolved at the moment is by downgrading to Nuxt 3.6.5, where it works normally.
Edit: Also tried 3.7.0 which results in the same slow loading.
The bug does not affect production builds, I ran the following command to test that:
yarn build && node .output/server/index.mjs
Additional context
No response
Logs
The text was updated successfully, but these errors were encountered: