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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@logto/next@3.4.0
Minor Changes
a40b28f: add getAccessToken to the server actions package
Previously, in order to get access tokens (and organization tokens) in App Router, you'll use
getLogtoContext
with config{ getAccessToken: true }
, this won't cache the token and will make a network request every time you call it. That is because Next.js does not allow to write cookies in the server side: HTTP does not allow setting cookies after streaming starts, so you must use .set() in a Server Action or Route Handler.This change adds a new function
getAccessToken
for you to get the access token in a server action or a route handler. It will cache the token and only make a network request when the token is expired.And also, this change adds a new function
getOrganizationToken
for you to get the organization token.The original method is deprecated and will be removed in the future.
ff8bcbb: support custom error handler for all methods in pages router
@logto/nuxt@0.3.3
Patch Changes
@logto/next-server-actions-sample@2.2.0
Minor Changes
a40b28f: add getAccessToken to the server actions package
Previously, in order to get access tokens (and organization tokens) in App Router, you'll use
getLogtoContext
with config{ getAccessToken: true }
, this won't cache the token and will make a network request every time you call it. That is because Next.js does not allow to write cookies in the server side: HTTP does not allow setting cookies after streaming starts, so you must use .set() in a Server Action or Route Handler.This change adds a new function
getAccessToken
for you to get the access token in a server action or a route handler. It will cache the token and only make a network request when the token is expired.And also, this change adds a new function
getOrganizationToken
for you to get the organization token.The original method is deprecated and will be removed in the future.
Patch Changes
@logto/next-app-dir-sample@2.1.17
Patch Changes
@logto/next-sample@2.1.17
Patch Changes