-
Notifications
You must be signed in to change notification settings - Fork 251
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
Navigo (^8.11.1) didn't match any of the registered routes #314
Comments
Same warning. How can I fix this problem? |
@delgec I fixed it by switching to navigo 7 |
I am also downgrade. Thanks for your reply. |
As I can see |
@ilteoood I did infact register the new-event page. I just didn't include it in the screenshot. |
@tielebodyn if you want to share a reproduction with stackblitz, I'm happy to help :) |
hi, I seem to be having a problem with Navigo 8.11.1.
when I make a singleton of Navigo, I seem to get an error every time I set my rootURL as anything except '/'. I tried http://localhost:1234, which is definitely the correct URL for my local server, but it keeps giving me the ''didn't match any of the registered routes" warning, as you can see in the image. when I use the '/' as root URL it loads my html and JS, but still gives me the same warning (even though it clearly does match my registered route).
I switched to version 7.0.0 and everything works perfectly.
PS: /new-event (from console warning) is a registered route, even though you can't see it an my Index.js
ref: https://stackoverflow.com/questions/73220543/navigo-javascript-routing-every-route-i-register-didnt-match-any-of-the-regist/73302262#73302262
Router.js code:
Index.js:
Console warning:
The text was updated successfully, but these errors were encountered: