feat: redirect kind#315
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
react-server-docs | 520478b | Commit Preview URL Branch Preview URL |
Feb 28 2026, 11:35 AM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a
kindparameter to theredirect()function, giving developers control over how redirects behave on the client side.Motivation
Resolves #289. The default redirect behavior (RSC navigation with
replaceState) isn't always what's needed. For example, OAuth flows require a full browser navigation, some redirects should preserve history for back-button support, and server actions sometimes need to signal a redirect to the client without automatically navigating.API
RedirectKindis a union of four values:"navigate"replaceState— same as current behavior"push"pushState— adds a history entry so the user can go back"location"location.href— useful for external URLs or OAuth flows"error"try/catchin server actions