Skip to content

Conversation

Milancen123
Copy link
Contributor

  • Added a Note to the Middleware docs explaining that when pageExtensions are customized (e.g. .page.ts), the Middleware file should be named middleware.page.ts or middleware.page.js.
  • Updated wording so middleware.ts/js is described as the default filename, not a strict requirement.

- Added a Note to the Middleware docs explaining that when `pageExtensions`
  are customized (e.g. `.page.ts`), the Middleware file should be named
  `middleware.page.ts` or `middleware.page.js`.
- Updated wording so `middleware.ts/js` is described as the default
  filename, not a strict requirement.
@ijjk ijjk added the Documentation Related to Next.js' official documentation. label Sep 21, 2025
@ijjk
Copy link
Member

ijjk commented Sep 21, 2025

Allow CI Workflow Run

  • approve CI run for commit: 8e3ca10

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

@icyJoseph
Copy link
Contributor

icyJoseph commented Sep 22, 2025

Edited the PR, I think this is important info, that should go into the flow of the document. Not just a note.

I also have #83693 open to document this further within pageExtensions itself. I do believe people who set pageExtensions start from the documentation page, or at least would go there in case of problem, so that's the likely point where you want to know all of the implications upfront.

Since I am still working on it, I think this patch to middleware docs is ok :)

@icyJoseph icyJoseph merged commit 2d96b96 into vercel:canary Sep 22, 2025
65 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Related to Next.js' official documentation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants