-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Router View and Suspense together break Reactivity #1114
Comments
Can you create a new git repo without the node_modules folder? |
Oh sorry! Didnt see that it got commited, let me just remove them quickly! |
Its cleaned up now! Same Repo, with gitignore and npmignore. Sorry for the inconvenience |
Your package.json doesn't have any deps, can you create a proper project with vite to show the problem? |
Uff sorry again, having a bad day! Updated the packages now! It runs with the newest vite version, vue-router and vue 3. |
Fixed un Vue |
Version
4.0.11
Reproduction link
github.com
As seen in this other reproduction via sfc created by @skirtles-code, this does only occur when
router-view
is added not onsuspense
only.Steps to reproduce
Using
suspense
androuter-view
as mentioned from the official Vue 3 Docs it runs into the issue that an increasing counter loses all reactivity inside the#fallback
area of suspense. Withoutrouter-view
everything works fine.What is expected?
Expected is that any variable (prop, ref etc) is holds its reactivity inside the
#fallback
slot same as default area. With or withoutrouter-view
.What is actually happening?
Adding
router-view
around suspense breaks reactivity on#fallback
slot.The text was updated successfully, but these errors were encountered: