-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
[client-only-path] is broken #1768
Comments
I have been having trouble with client only routes for some time. I am not sure if it was related to gatsby or some funky stuff I was trying so I don't know which version of Gatsby to go back to. I'd be grateful if someone can point me to a safe package combo. |
oh and I just remembered that maybe we have to pass the location from the layout down to pages but when we do, we get:
|
Wow I am dumb! I just figured that my So, problem solved. Really sorry for the written pollution. =/ For reference in case someone land here, the solution is right in the docs: https://www.gatsbyjs.org/docs/creating-and-modifying-pages/#creating-client-only-routes |
gatsby 1.8.1
Basically React-Router navigation is broken. The index Route (so the Route with path = name of page where the router is defined) is fine but we get into trouble when navigating to sub-routes.
With the client-only-path example, the index page shows up when we navigate to sub-routes which is probably why the example site does not fail at first look (when only the index page is defined and all routes start there).
On my website on the other hand I either land on the dev-404-page or I get the following error when navigating to sub-routes:
To reproduce with gatsby example site:
gatsby develop
The text was updated successfully, but these errors were encountered: