Feature Request: Support serviceUnavailable() function for 503 errors in Next.js

[hamzamongam]

In Next.js, notFound() is available to handle 404 errors, but there's no built-in function like serviceUnavailable() for handling 503 errors.

Problem:

• Currently, to handle a 503 error, we need to manually throw an error and catch it in global-error.tsx.
• This limits the ability to customize HTTP status codes directly from Next.js components or routes.

Proposal:

• Introduce a serviceUnavailable() helper, similar to notFound(), which would raise an HTTP 503 status and allow rendering a custom error page.

Example:

  import { serviceUnavailable } from 'next/navigation';

  export async function GET() {  
      serviceUnavailable();  
} 

This would improve error handling consistency and allow more granular control over HTTP responses.

[hamzamongam]

any updates

[axten]

We came across the same thing in our projects and would love the find a solution for handling 50x errors.
Another possible idea is, that we get rid of all the different functions and templates and have a more generic error function:

import { error } from 'next/navigation';

  export async function GET() {  
      error(502);  
}

[icyJoseph]

There's the https://nextjs.org/docs/app/api-reference/config/next-config-js/authInterrupts experiment, we shall see where that goes. Discussion thread, #73753