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.
Next.js 410 Gone Status Feature
This PR adds support for HTTP 410 Gone status in Next.js, providing developers with a way to indicate that content has been permanently removed. This is an important status code for SEO and user experience, as it differentiates between content that doesn't exist (404) and content that previously existed but has been deliberately removed (410).
Features
gone()
function for App Routergone: true
in getServerSideProps and getStaticProps for Pages Routergone.js
file convention similar tonot-found.js
Implementation Details
This PR implements:
App Router Support:
gone()
function in thenext/navigation
modulegone.js
file convention for customizing the 410 error pagePages Router Support:
{ gone: true }
from data fetching functions/410
page support similar to/404
pageAPI Route Support:
Documentation
Tests
The PR includes:
gone()
functionExample Usage
App Router
Pages Router
Example Project
An example project is included in
gone-status
demonstrating both App Router and Pages Router implementations of the feature.Breaking Changes
None. This is a new feature with no changes to existing behavior.
Fixes #18684
Extends #73753