Skip to content
Discussion options

You must be logged in to vote

This could be many things but it's likely a blocking navigation guard with some API call. It's very unlikely to be at the router level.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by posva
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants