-
Notifications
You must be signed in to change notification settings - Fork 5
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
Client side navigation #2
Comments
I can reproduce this. This repository is auto-synced from opral/monorepo, so there is the possibility that something is going wrong there |
Not really sure what's going on TBH. The exact same code does run in opral/monrepo. Might be a case of incompatible dependencies. Will have to look further |
Hi @LorisSigrist thanks for digging in to this I did do some version mashing to see if it helped but I wasn't able to look into it deeply yet. I will try and narrow the issue to some of the upstream components and raise an issue there if I find anything |
This was most likely caused by vitejs/vite#16245 & will be fixed in the next vite version |
I installed the project, ran
npm install
npm start
, and client side navigation appears to be broken.requests to
localhost:5174/
andlocalhost:5174/about/
work as expected, requests viacurl
look like normal sveltekit requests.However, refreshing the page or clicking on the links result in requests that sveltekit does not handle, eventually timing out (from the client side).
Maybe a version mishmash? If I can help debug in any way, please let me know!
The text was updated successfully, but these errors were encountered: