Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Update docs following Next.js 16 middleware filename change #2745

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 13 commits into from
Oct 28, 2025
Merged

Update docs following Next.js 16 middleware filename change #2745

merged 13 commits into from
Oct 28, 2025
+105 −61

Conversation

@SarahSoutoul
Copy link
Contributor

@SarahSoutoul SarahSoutoul commented Oct 27, 2025 •
edited
Loading

🔎 Previews:

What does this solve?

One of the changes included in Next.js 16 is the change of name from middleware.ts to proxy.ts. A user on the new version would still be able to use middleware.ts, but if someone on a older version of Next.js uses proxy.ts, things would break. This PR updates the docs to reflect on this change via a callout + renaming of file for code snippets.

What changed?

  • Added a partial containing a callout that appears in all pages referring to the middleware.ts file.
  • Renamed the code snippets filenames to show the new naming.

Note: Open to other suggestions on how to show this change. I'm not convinced we need the partial/callout on all pages.

Checklist

  • I have clicked on "Files changed" and performed a thorough self-review
  • All existing checks pass

@SarahSoutoul SarahSoutoul self-assigned this Oct 27, 2025
@vercel
Copy link

vercel bot commented Oct 27, 2025 •
edited
Loading

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

Project Deployment Preview Updated (UTC)
clerk-docs Ready Ready Preview Oct 28, 2025 7:56pm

@SarahSoutoul SarahSoutoul marked this pull request as ready for review October 27, 2025 18:19
@SarahSoutoul SarahSoutoul requested a review from a team as a code owner October 27, 2025 18:19
@alexisintech
Copy link
Member

our rule has been that the docs reflect whatever the latest version is - so all of these should be proxy.ts instead of middleware|proxy.ts

I agree that the callout should reflect that if the user is on an earlier version of Next.js, they need to use middleware.ts instead of proxy.ts - but I don't think we should be halving the file names like the current PR suggests. I think it might be too confusing :/

@SarahSoutoul
Copy link
Contributor Author

our rule has been that the docs reflect whatever the latest version is - so all of these should be proxy.ts instead of middleware|proxy.ts

I agree that the callout should reflect that if the user is on an earlier version of Next.js, they need to use middleware.ts instead of proxy.ts - but I don't think we should be halving the file names like the current PR suggests. I think it might be too confusing :/

Okay sounds good. This is the sanity check I needed - thanks @alexisintech!

@SarahSoutoul
Copy link
Contributor Author

@alexisintech have renamed all the middleware.ts files to proxy.ts, and updated the callout. Let me know thoughts!

alexisintech
alexisintech reviewed Oct 28, 2025
View reviewed changes
@SarahSoutoul SarahSoutoul merged commit 33c2605 into main Oct 28, 2025
8 checks passed
@SarahSoutoul SarahSoutoul deleted the ss/DOCS-11099 branch October 28, 2025 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@alexisintech alexisintech alexisintech approved these changes

@manovotny manovotny Awaiting requested review from manovotny

Assignees

@SarahSoutoul SarahSoutoul

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@SarahSoutoul @alexisintech