-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
#16135 introduced development server bug #16245
Comments
I won't be back at a computer for a while to gather more info, but I am not using paraglide. There's also an issue on the sveltekit repo for this sveltejs/kit#12020 |
Came here to post the same bug, thanks for detailing the issue. |
I have a repro of the bug, pre-and-post v5.1.6 Vite: https://github.com/arxpoetica/inlang-sveltekit-vite-bug I tried to reproduce this on StackBlitz for easier debugging, but that was creating issues on its own. |
Thanks for creating the issue, and thanks for the repro @arxpoetica 🙏🏼 I'll run ecosystem-ci on it, and let you try it out. I'll merge it and do a release tomorrow. |
Can confirm this fixed it, thanks! |
Describe the bug
vite dev
boots up the server, but it doesn't respond to several file requests, causing the page to infinitely loadAffected vite plugin (in my case): @inlang/paraglide-js-adapter-sveltekit
@knd775 probably has other affected plugin (as paraglide tool it not very popular), but we don't know which one yet.
I can confirm that #16135 introduced a bug. I have built vite locally and all commits after 5.2.0-beta.0 and before #15135 work fine.
More info: #16135 (comment) 1220740873273475162 (discord thread)
UPD0: I have tried to reproduce the issue without sveltekit, no luck.
UPD1: Sveltekit issue sveltejs/kit#12020
Reproduction
https://git.sr.ht/~zerdox/paraglide-js-adapter-sveltekit_incompatibility_vite-5.2.0-beta.1
Steps to reproduce
pnpm i
pnpm run dev
orpnpm vite dev
Probably could be reproduced with other package managers too.
System Info
Used Package Manager
pnpm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: