Files
69388a52fe Partial Prerendering (#57287)
This PR introduces a build optimization to create a "partial prerender" of the page.

1. During compilation, we create a static shell for the page using your existing Suspense boundaries. Components that can be static will be included in this static shell, leaving holes for the dynamic components.
1. Using `<Suspense />`, we can define fallbacks to be included in the partial prerender, as well as the holes for the dynamic components to stream into.

This means Next.js can initially serve a static loading skeleton, kicking off the dynamic parts in parallel. Then, the dynamic components stream in on demand. Dynamic components can use `cookies()`, `headers()`, `'cache': 'no-store'`, or `unstable_noStore()` to opt-into dynamic rendering.

Co-authored-by: Zack Tanner <[email protected]>
2023-10-24 01:13:05 +00:00

22 lines
543 B
JavaScript

import { cookies } from 'next/headers'
export function POST(request) {
const url = new URL(request.url)
const name = url.searchParams.get('name')
if (!name) {
return new Response(null, { status: 400 })
}
cookies().set(name, '1')
return new Response(null, { status: 204 })
}
export function DELETE(request) {
const url = new URL(request.url)
const name = url.searchParams.get('name')
if (!name) {
return new Response(null, { status: 400 })
}
cookies().delete(name)
return new Response(null, { status: 204 })
}