cloudflare/vinext

Server actions: request tracker never intercepts action POST when node-runtime middleware is configured

已关闭

#1,480 创建于 2026年5月22日

 (0 条评论) (0 个反应) (0 位负责人)TypeScript (384 个派生)github user discovery
adapter-api-e2ehelp wanted

仓库指标

星标
 (8,625 个星标)
PR 合并指标
 (平均合并 1天 1小时) (30 天内合并 462 个 PR)

描述

This issue was created by an agent analysing CI failures from the Next.js Deploy Suite (vinext main vs Next.js v16.2.6, 2026-05-22).

Problem

Tests that invoke a server action with a serverActions.bodySizeLimit config under a node-runtime middleware never see the expected action POST request fire (Did not intercept a request within 5000ms). The action endpoint appears to be short-circuited by the node middleware instead of being dispatched.

Did not intercept a request within 5000ms (server action POST under node middleware)

Estimated Impact

~5 test failures across the deploy suite.

Affected Test Suites

  • test/e2e/app-dir/actions/app-action-size-limit-invalid-node-middleware.test.ts (5 failures)

Recommendation

  1. Reproduce first in vinext's own test suite. Add a server action inside an app that also defines a node-runtime middleware.ts. Submit the action and assert the POST request is observed by the test runner.

  2. Route action POSTs through middleware properly. Ensure that, after node middleware decides to fall through, the server-action POST is dispatched to the action handler rather than being swallowed.

  3. Also check the bodySizeLimit enforcement path. The original suite is app-action-size-limit-invalid-node-middleware; verify the body-size-limit enforcement still runs after middleware.

贡献者指南