-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
fix(nuxt): trigger call once navigation even when no suspense #32827
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
Conversation
|
WalkthroughThe changes update the mechanism by which the Estimated code review effort🎯 2 (Simple) | ⏱️ ~7 minutes Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
✨ Finishing Touches
🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
@nuxt/kit
nuxt
@nuxt/rspack-builder
@nuxt/schema
@nuxt/vite-builder
@nuxt/webpack-builder
commit: |
CodSpeed Performance ReportMerging #32827 will not alter performanceComparing Summary
|
The only scenario I could think of that could be different would be triggering when a |
@danielroe this doesn't solve the issue unless the behavior you expect is different from what i thought in the original issue. The repro is still the same but with nuxt dependency set at 4.0.3. the callback is still not executed on client side routing |
callOnce does not automatically re-call the handler, and you called it in app.vue setup, which only runs once. you could recall it in a watcher. |
I'm trying not to sound passive aggressive, but the docs say it will, specifically on client side navigation. What is the difference between the modes and importantly what should occur? |
the docs may be unclear the idea is if you call it in a page it will only run again if mode: navigation is set it won't automatically run on navigation - you have to call it again |
🔗 Linked issue
resolves #32811
📚 Description
page:start
is only called when suspense initiates, meaning the previous implementation did not resetcallOnce
when synchronous navigation took place.was there a reason we didn't use the router originally @TheAlexLichter?