cloudflare/vinext

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

Geschlossen

#1.480 geöffnet am 22.05.2026

 (0 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)TypeScript (383 Forks)github user discovery
adapter-api-e2ehelp wanted

Repository-Metriken

Stars
 (8.624 Sterne)
PR-Merge-Metriken
 (Durchschn. Merge 1T 1h) (462 gemergte PRs in 30 T)

Beschreibung

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.

Contributor Guide