Routing Information

The routing object in onBuildComplete provides complete routing information with processed patterns ready for deployment:

routing.beforeMiddleware

Routes applied before middleware execution. These include generated header and redirect behavior.

routing.middlewareMatchers

Middleware matcher definitions emitted for this build. Use these to decide whether middleware should be invoked for a given request.

routing.beforeFiles

Rewrite routes checked before filesystem route matching.

routing.afterFiles

Rewrite routes checked after filesystem route matching.

routing.dynamicRoutes

Dynamic matchers generated from route segments such as [slug] and catch-all routes.

routing.onMatch

Routes that apply after a successful match, such as immutable cache headers for hashed static assets.

routing.fallback

Final rewrite routes checked when earlier phases did not produce a match.

Common Route Fields

Each route entry can include:

• source: Original route pattern (optional for generated internal rules)
• sourceRegex: Compiled regex for matching requests
• destination: Internal destination or redirect destination
• headers: Headers to apply
• has: Positive matching conditions
• missing: Negative matching conditions
• status: Redirect status code
• priority: Internal route priority flag