TS · correctness

←Previous Next→

require-static-next-matcher

Require Next.js middleware and proxy matcher configuration to contain only build-time literals.

dynamicMatcher Rule source Tests Catalog JSON

Why

Next.js must statically analyze matcher values at build time; computed values are ignored.

Fix

Write matcher strings, arrays, and object fields as literals in the exported config.

Examples

Before — flagged Do not compute the matcher

src/middleware.ts

const matcher = "/api/:path*";
export const config = { matcher };

After — preferred Use a literal matcher

src/middleware.ts

export const config = { matcher: "/api/:path*" };

References

• https://nextjs.org/docs/app/api-reference/file-conventions/proxy