The HTTP methods supported are: GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS. request (optional) and context(optional) carrying params are props received.

Describe route.js.

Difficulty: 6/10

Route Handlers, Next.js App Router, API Caching

Route Handlers allow you to create custom request handlers for a given route using the Web Request and Response APIs.

1
The HTTP methods supported are: GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS.
2
request (optional) and context(optional) carrying params are props received.

Scenario Questions

0-2 years experience

1Imagine you need to build a simple webhook endpoint at `/api/stripe-webhook` that only accepts POST requests and returns a JSON success message. How would you set up the folder structure and write the `route.js` file to handle this?
2You've written a GET handler in `app/api/time/route.js` to return the current server time, but users are complaining that it always returns the exact same time. What's causing this caching behavior, and how would you fix it so it returns the fresh time on every request?

Follow-up Questions

How does Next.js determine if a route handler should be statically cached or executed dynamically?
What happens if you define both a page.js and a route.js in the same route segment?
How do you access dynamic route parameters inside a route.js handler?