feat(edge): Add Auth-Result observability header to Vercel Edge middl… #196
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.
Type of change
Packages affected
@clerk/clerk-js
@clerk/clerk-react
@clerk/nextjs
@clerk/remix
@clerk/types
@clerk/clerk-expo
@clerk/backend-core
@clerk/clerk-sdk-node
@clerk/edge
build/tooling/chore
Description
npm test
runs as expected.npm run build
runs as expected.Auth-Result
observability header on Vercel-Edge middleware.The possible values of a handler is
Response | NextResponse | null | undefined
so in any case we are covered by using the.?
access on the response object to set the headers.https://www.notion.so/clerkdev/Add-Auth-Result-header-on-Next-js-edge-_middleware-38752519809d417c9a25ca40b6d6d4e8