feat(platform): Run middleware on node#16642
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
sergical
approved these changes
Mar 2, 2026
Contributor
There was a problem hiding this comment.
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, | ||
| }, |
Contributor
There was a problem hiding this comment.
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.
Next.js 15.5 changed how React children are serialized during SSR, which can result in child elements with undefined props being passed to CodeTabs. Filter these out before destructuring. Co-Authored-By: Claude <noreply@anthropic.com>
chargome
added a commit
that referenced
this pull request
Mar 4, 2026
6 tasks
sergical
added a commit
that referenced
this pull request
Mar 4, 2026
Re-applies the changes from #16642 (reverted in #16685) with the env var fix in place: middleware now falls back to NEXT_PUBLIC_DEVELOPER_DOCS when DEVELOPER_DOCS_ isn't available at runtime. Changes: - Upgrade Next.js 15.1 → 15.5.12 - Enable experimental.nodeMiddleware in next.config.ts - Set runtime: 'nodejs' in middleware config - Move pages/ to root (required by Next.js 15.5 node middleware) - Filter falsy children in CodeTabs (Next.js 15.5 compat) Co-Authored-By: Claude <noreply@anthropic.com>
sergical
added a commit
that referenced
this pull request
Mar 4, 2026
Re-applies the changes from #16642 (reverted in #16685) with the env var fix in place: middleware now falls back to NEXT_PUBLIC_DEVELOPER_DOCS when DEVELOPER_DOCS_ isn't available at runtime. Changes: - Upgrade Next.js 15.1 → 15.5.12 - Enable experimental.nodeMiddleware in next.config.ts - Set runtime: 'nodejs' in middleware config - Move pages/ to root (required by Next.js 15.5 node middleware) - Filter falsy children in CodeTabs (Next.js 15.5 compat) Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Switches the runtime for middleware invocations from
edgetonode.ref https://vercel.com/changelog/middleware-now-supports-node-js