-
Notifications
You must be signed in to change notification settings - Fork 98
Description
Environment
- Operating System: Linux (WSL on Windows 11)
- Node Version: v18.15.0
- Nuxt Version: 3.7.1
- CLI Version: 3.8.3
- Nitro Version: 2.6.3
- Package Manager: yarn@1.22.19
- Builder: -
- User Config: devtools
- Runtime Modules: -
- Build Modules: -
Reproduction
- Open a WSL cli.
- Run the init command
npx nuxi@latest init my-app
and choose yarn as the package manager. (just for fun I also tried it with bun, same problem) - Start the server using
yarn dev
. - Open the page in a a browser, preferably private mode.
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
No logs, the network tab is the only place where I can see anything related to this problem.