Skip to content
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

chore(docs): fix middleware verbiage #5981

Merged
merged 3 commits into from Dec 31, 2022
Merged

chore(docs): fix middleware verbiage #5981

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
16c927d
Make documentation easier to understand
ndisalvio3 Dec 7, 2022
ca15b26
Merge branch 'main' into patch-1
ndom91 Dec 12, 2022
356ad8a
Apply suggestions from code review
balazsorban44 Dec 31, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/docs/tutorials/securing-pages-and-api-routes.md
View file
Open in desktop
Expand Up @@ -42,7 +42,7 @@ export default function Page() {

### Next.js (Middleware)

With NextAuth.js 4.2.0 and Next.js 12, you can now protect your pages via the middleware pattern more easily. If you would like to protect all pages, you can create a `middleware.js` file in your root `pages` directory which looks like this:
With NextAuth.js 4.2.0 and Next.js 12, you can now protect your pages via the middleware pattern more easily. If you would like to protect all pages, you can create a `middleware.js` file in your root directory which looks like this:
balazsorban44 marked this conversation as resolved.
Show resolved Hide resolved

```js title="/middleware.js"
export { default } from "next-auth/middleware"
Expand Down