-
-
Notifications
You must be signed in to change notification settings - Fork 476
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
Warning loop since router update in nuxt 2.3.4/1.4.5 #160
Comments
ghost
added
the
cmty:bug-report
label
Nov 28, 2018
It's this bug: vuejs/vue-router#2505 |
Duplicate/out of scope |
farnabaz
added a commit
to farnabaz/i18n-module
that referenced
this issue
Mar 25, 2021
* vite + windicss * update deps * update extensions * revert content watch * chore: disable ssr in dev * revert windicss * chore: revert * remove vite include * cleanup docus-ui * prevent infinite loop on vite start * disbale ssr render and build in dev * chore: update style * chore: upgrade tailwind * fix: improve compatibility * fix: mock unused libraries with default exports * fix: remove unneeded changes * fix: remove uneeded vite config * refactor: move aliases to right config * move mock into theme * chore: update deps Co-authored-by: Farnabaz <farnabaz@gmail.com> Co-authored-by: Sébastien Chopin <seb@nuxtjs.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v5.4.4
Reproduction link
https://codesandbox.io/s/y7pqv48y19
Steps to reproduce
Navigate to the dynamic route, console is spammed with loop of "[vue-router] missing param for named route "test-all___en": Expected "0" to be defined", in client when navigating, or in server when going directly.
What is expected ?
Should not produce warnings.
What is actually happening?
Produces warnings when the route is manually localized in nuxt config.
Additional comments?
This is maybe a consequence of the new handling of dynamic route params in vue-router 3.0.2. Also happens in nuxt 1.4.5, which has the updated vue-router.
The text was updated successfully, but these errors were encountered: