rsnext/test/e2e/app-dir/navigation
Wyatt Johnson 252d9cf453
Navigation Signals in PPR (#60450)
### What

This adds support for navigation signals like `notFound()` and
`redirect(url)` when Partial Prerendering has been enabled.

### Why

Navigation API's like `notFound()` and `redirect(url)` throw errors in
order to interrupt the rendering of components. When a page both invokes
API's that cause the render to be marked as dynamic (like
`unstable_noStore()`) and also a navigation API, these errors may race
to the end. In the case where the navigation error does not beat out the
error emitted by dynamic API's will still trigger the detection warning
that's present to warn you about situations where you may have
accidentally caught the error.

### How

This resolves this issue by explicitly checking for navigation signals
(errors) thrown during the render, and not displaying the "caught
dynamic API" error and console warning.

Closes NEXT-2037
2024-02-06 12:25:50 -07:00
..
app fix navigation issue when dynamic param casing changes (#61726) 2024-02-06 08:59:18 -08:00
pages memoize useParams (#56771) 2023-10-13 07:47:05 +00:00
middleware.js Export RedirectType from next/navigation (#54729) 2023-08-29 11:05:44 -07:00
navigation.test.ts Navigation Signals in PPR (#60450) 2024-02-06 12:25:50 -07:00
next.config.js Remove experimental config from create-next-app (#49241) 2023-05-05 00:22:28 -07:00