Deprecate createRouteMatcher in Nuxt docs in favor of built-in route protection#3406
Open
jacekradko wants to merge 1 commit into
Open
Conversation
…protection Rewrites the Nuxt protect-pages guide to use Nuxt's named route middleware (definePageMeta inheritance) and route groups (route.meta.groups, Nuxt 4.3+) instead of createRouteMatcher, updates the overview accordingly, and switches the clerkMiddleware API-route examples to event.path prefix checks (also destructuring has() correctly).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Stacked on #3405. Moves the Nuxt docs off
createRouteMatcherto Nuxt's built-in route protection.protect-pages.nuxtnow uses named route middleware (definePageMetawith file-system inheritance) and route groups (route.meta.groups, Nuxt 4.3+) instead of matching paths by hand, and the API-route examples in the middleware reference useevent.pathprefix checks. While rewriting the authorization example I also destructuredhas()fromevent.context.auth(), which was previously referenced but never defined.