Skip to content

fix: inline proxy config so Next can statically read the matcher#420

Merged
drankou merged 1 commit into
mainfrom
fix-proxy
Jun 16, 2026
Merged

fix: inline proxy config so Next can statically read the matcher#420
drankou merged 1 commit into
mainfrom
fix-proxy

Conversation

@drankou

@drankou drankou commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Next statically parses config from proxy.ts at build time and can't follow a re-export. The #417 refactor re-exported config from runtime.ts, breaking the parse — dev 500'd and prod dropped the matcher (proxy ran on all requests). Inline config as a literal in proxy.ts and remove the duplicate from runtime.ts. The proxy function re-export is fine (resolved at runtime).

Next statically parses `config` from `proxy.ts` at build time and can't follow
a re-export. The #417 refactor re-exported `config` from `runtime.ts`, breaking
the parse — dev 500'd and prod dropped the matcher (proxy ran on all requests).
Inline `config` as a literal in `proxy.ts` and remove the duplicate from
`runtime.ts`. The `proxy` function re-export is fine (resolved at runtime).
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

@vercel

vercel Bot commented Jun 16, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
web Ready Ready Preview, Comment Jun 16, 2026 12:13pm

Request Review

@drankou drankou merged commit f053ec0 into main Jun 16, 2026
13 checks passed
@drankou drankou deleted the fix-proxy branch June 16, 2026 12:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants