Skip to content

Support "missing" middleware matcher #1796

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
Closed
ascorbic opened this issue Nov 22, 2022 · 0 comments · Fixed by #1905
Closed

Support "missing" middleware matcher #1796

ascorbic opened this issue Nov 22, 2022 · 0 comments · Fixed by #1905
Assignees
@taty2010

Comments

@ascorbic
Copy link
Contributor

ascorbic commented Nov 22, 2022 •
edited
Loading

Next.js now supports "missing" as a new matcher key. This doesn't seem to be documented yet, but it was merged in this PR and released in 13.0.3: https://github.com/vercel/next.js/pull/42660. The e2e test for this is middleware-custom-matchers.
@ascorbic ascorbic changed the title Support "missing" middleware matcher Support "missing" middleware matcher Dec 15, 2022
@taty2010 taty2010 self-assigned this Jan 20, 2023
@taty2010 taty2010 mentioned this issue Jan 24, 2023
Merged
2 tasks
@kodiakhq kodiakhq bot closed this as completed in #1905 Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@taty2010 taty2010

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: added support for "missing" matcher opennextjs/opennextjs-netlify
2 participants
@ascorbic @taty2010