Skip to content

feat(platform): Run middleware on node#16642

Open
chargome wants to merge 3 commits intomasterfrom
cg/node-middleware
Open

feat(platform): Run middleware on node#16642
chargome wants to merge 3 commits intomasterfrom
cg/node-middleware

Conversation

@chargome
Copy link
Member

@chargome chargome commented Mar 2, 2026

Switches the runtime for middleware invocations from edge to node.

ref https://vercel.com/changelog/middleware-now-supports-node-js

@chargome chargome self-assigned this Mar 2, 2026
@vercel
Copy link

vercel bot commented Mar 2, 2026

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

Project Deployment Actions Updated (UTC)
develop-docs Error Error Mar 2, 2026 2:15pm
sentry-docs Error Error Mar 2, 2026 2:15pm

Request Review

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

},
experimental: {
nodeMiddleware: true,
},
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Redundant experimental flag for stable Node.js middleware

Low Severity

The experimental.nodeMiddleware flag in next.config.ts is unnecessary with Next.js 15.5, where Node.js middleware is a stable feature. The runtime: 'nodejs' in the middleware config export (src/middleware.ts) is the only configuration needed. Having the redundant experimental flag suggests the feature is still experimental and may confuse future maintainers.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants