Proxy configuration causes unnecessary empty data requests in Next.js.
The issue involves proxy configuration in Next.js causing unnecessary empty data requests to `_next/data`. A potential solution exists via a pnpm patch, but it's unclear if this affects other parts of the system or if it's the correct architectural approach. The problem is reproducible but involves middleware which is deprecated.
https://github.com/ari-party/repro-next-data-empty-object
_next/data request for each link to a page{}Current: Requests made to _next/data/*/*.json
Expected: No requests made to _next/data/*/*.json
These empty data files bring no value and may cause a client error if the app is rebuilt, even if assetPrefix with hash is used.
Operating System:
Platform: linux
Arch: x64
Version: #35~22.04.1-Ubuntu SMP Mon May 26 18:08:30 UTC 2025
Available memory (MB): 7944
Available CPU cores: 2
Binaries:
Node: 24.11.1
npm: 11.6.2
Yarn: 1.22.22
pnpm: 10.23.0
Relevant Packages:
next: 16.1.6 // Latest available version is detected (16.1.6).
eslint-config-next: 13.5.6
react: 18.2.0
react-dom: 18.2.0
typescript: 5.3.3
Next.js Config:
output: N/A
Middleware, Pages Router
next start (local)
This a recreation of an older issue https://github.com/vercel/next.js/issues/59295. This issue is present for both the deprecated middleware and the newer proxy.
Additionally might be related: https://github.com/vercel/next.js/issues/59612
Claim this issue to let others know you're working on it. You'll earn 20 points when you complete it!