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.

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

fix(nextjs): Make exported server action async #3593

Merged
merged 3 commits into from
Jun 19, 2024

Conversation

BRKalow
Copy link
Member

@BRKalow BRKalow commented Jun 19, 2024

Description

Fixes a reported issue where the following error was reported: https://nextjs.org/docs/messages/invalid-use-server-value

I'm not able to reproduce myself across a number of versions, but based on the documentation above, this function must be async, so I'm updating it.

Checklist

  • npm test runs as expected.
  • npm run build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Copy link

changeset-bot bot commented Jun 19, 2024

🦋 Changeset detected

Latest commit: 93ec058

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@clerk/nextjs Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

@louisgv louisgv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@nikosdouvlis nikosdouvlis merged commit 1e57618 into main Jun 19, 2024
4 checks passed
@nikosdouvlis nikosdouvlis deleted the brk.fix/invalidate-cache-action-async branch June 19, 2024 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants