nextauthjs / nextauthjs/next-auth
bug: lost asyncLocalStorage in server actions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 28.4k
- Forks
- 4k
- PR merge metrics
- No merged PRs in 30d
Description
Environment
System:
OS: macOS 13.3.1
CPU: (8) arm64 Apple M1 Pro
Memory: 926.67 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.16.0 - ~/Library/Caches/fnm_multishells/3962_1684784742591/bin/node
Yarn: 1.22.19 - ~/Library/Caches/fnm_multishells/3962_1684784742591/bin/yarn
npm: 9.5.1 - ~/Library/Caches/fnm_multishells/3962_1684784742591/bin/npm
Browsers:
Safari: 16.4
Reproduction URL
coming soon
Describe the issue
How to reproduce
Call getServerSession inside a server action
Expected behavior
session retrieval to be successful
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue at the getServerSession entry point inside a Next.js server action, using the reported Node 18.16.0 environment and the provided screenshot as context. Done means session retrieval succeeds without losing asyncLocalStorage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, node.js, typescript
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100