You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You need vite (5.1.6) app and a framework that employs HMR, e.g. SvelteKit
The app needs to fetch something externally, e.g. from a db and after an npm update and vite restart, the whole app produces weird errors not able to get backend data (see below)
The only fix is turning on and of wifi, I have rock-solid Intel Wifi cards
READ: I tested all possible parts, SvelteKit, vite, DB, and whatever and once I tested the app on a spare notebook which hasn't updated to the latest WSL version it worked flawlessly, unfort. IDK that old version anymore but I think I have never updated WSL (2) on that notebook. Once I updated to the latest version on that notebook, it broke as well 😒
I cannot provide a better reproduction, slimming down my app to some repro repo would take 10x more time than just spinning up some real Linux VM somewhere and continue my work there. So, you guys needs to create this repro repo yourself and/or maybe this behavior sounds familiar to you and you have some guess s where we can look at. Again, I cannot create the repro without any commitment from your side that someone gets really involved.
This is severe because it's a dealbreaker and so hard to reproduce and debug. Happy to help where I can and good luck.
Edit: I could offer doing a kind of git bisect, pls let me know how I can install older versions of wsl and I can try to find the 'bad' version that intro'd the regression.
Edit2: FWIW, I have the project folder in WSL2 and not in Windows
Expected Behavior
no errors after an npm update and vite restart
Actual Behavior
in that vite/SvelteKit app in Chrome Inspector, I get:
[HMR][Svelte] Unrecoverable HMR error in <Layout>: next update will trigger a full reload
then errors such as
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading '$$'
Again, the cause is WSL2, recent versions
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered:
Hi I'm an AI powered bot that finds similar issues based off the issue title.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!
Windows Version
Microsoft Windows [Version 10.0.22631.3296]
WSL Version
WSL version: 2.1.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.146.1-2
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
READ: I tested all possible parts, SvelteKit, vite, DB, and whatever and once I tested the app on a spare notebook which hasn't updated to the latest WSL version it worked flawlessly, unfort. IDK that old version anymore but I think I have never updated WSL (2) on that notebook. Once I updated to the latest version on that notebook, it broke as well 😒
I cannot provide a better reproduction, slimming down my app to some repro repo would take 10x more time than just spinning up some real Linux VM somewhere and continue my work there. So, you guys needs to create this repro repo yourself and/or maybe this behavior sounds familiar to you and you have some guess s where we can look at. Again, I cannot create the repro without any commitment from your side that someone gets really involved.
This is severe because it's a dealbreaker and so hard to reproduce and debug. Happy to help where I can and good luck.
Edit: I could offer doing a kind of git bisect, pls let me know how I can install older versions of wsl and I can try to find the 'bad' version that intro'd the regression.
Edit2: FWIW, I have the project folder in WSL2 and not in Windows
Expected Behavior
no errors after an npm update and vite restart
Actual Behavior
in that vite/SvelteKit app in Chrome Inspector, I get:
then errors such as
Again, the cause is WSL2, recent versions
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: