sincecutoff.com
/v1/json /v1/md llms.txt
← all changes

Vercel Node.js Routing Middleware supports proxy entrypoints and matchers

Introduced 2026-07-27 · score 0.93

HOW TO USE IT

When configuring Node.js Routing Middleware with a project entrypoint, set `proxy.entrypoint` in `vercel.json`; if path filtering is needed, set `proxy.matcher` in `vercel.json` or matcher config in the entrypoint, but not both.

{"$schema":"https://openapi.vercel.sh/vercel.json","proxy":{"entrypoint":"<path-to-entrypoint>","matcher":["<path-pattern>"]}}
export const config = { matcher: "<path-pattern>" };

WHY THIS HELPS

Configure Node.js Routing Middleware for a project entrypoint and optional path matching.

REQUIREMENTS AND LIMITATIONS

  • Version: 58.0.0
  • proxy.entrypoint (required): Path to the Routing Middleware entrypoint; set it in `vercel.json` to use a different filename or directory.
  • proxy.matcher: A string or array of strings defining the paths on which the Routing Middleware runs; configure here or in the entrypoint, not both.
  • config.matcher: A string or array of strings defining the paths on which the Routing Middleware runs when configured in the entrypoint source.
  • The matcher may be configured in the entrypoint source or `vercel.json`, but not both.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card