138361208c
This PR removes the duplicate overview link for data fetching, and fixes the corresponding links ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `yarn lint` Co-authored-by: Lee Robinson <9113740+leerob@users.noreply.github.com> Co-authored-by: JJ Kasper <22380829+ijjk@users.noreply.github.com>
1.1 KiB
1.1 KiB
Rewriting to Auto Export or Fallback Dynamic Route
Why This Error Occurred
One of your rewrites in your next.config.js
point to a dynamic route that is automatically statically optimized or is a fallback SSG page.
Rewriting to these pages are not yet supported since rewrites are not available client-side and the dynamic route params are unable to be parsed. Support for this may be added in a future release.
Possible Ways to Fix It
For fallback SSG pages you can add the page to the list of prerendered paths.
For static dynamic routes, you will currently need to either rewrite to non-dynamic route or opt the page out of the static optimization with getServerSideProps