Use Cases

Core Idea

Enumerates the common reasons a team builds a Next.js deployment adapter, as a quick orientation before diving into the API reference.

Deployment Platform Integration: automatically configure build outputs for a specific hosting platform.
Asset Processing: transform or optimize build outputs.
Monitoring Integration: collect build metrics and route information.
Custom Bundling: package outputs in platform-specific formats.
Build Validation: ensure outputs meet specific requirements.
Route Generation: use processed route information to generate platform-specific routing configs.

This page is a short catalog, not an API surface — six one-line use cases for why an adapter exists.
"Route Generation" and "Deployment Platform Integration" are the two most common real-world adapter purposes (translating routing/outputs into a platform's native config).

ch270 adapters: parent index page.
ch279 output-types / ch280 routing-information: the data these use cases operate on.