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

chore(docs): Describe how to avoid Next.js route handler auth type conflict with explicit type casting #11729

Closed
wants to merge 2 commits into from

Conversation

SongDerrick
Copy link

☕️ Reasoning

No description to avoid next.js type check build failure when explicit type casting is omitted.

🧢 Checklist

  • Documentation
  • [] Tests
  • Ready to be merged

🎫 Affected issues

📌 Resources

Copy link

vercel bot commented Aug 30, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
auth-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 2, 2024 8:25am
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
next-auth-docs ⬜️ Ignored (Inspect) Visit Preview Sep 2, 2024 8:25am

Copy link

vercel bot commented Aug 30, 2024

@SongDerrick is attempting to deploy a commit to the authjs Team on Vercel.

A member of the Team first needs to authorize it.

@ThangHuuVu
Copy link
Member

What error are you running to?

@SongDerrick
Copy link
Author

SongDerrick commented Aug 31, 2024

Type error: Route "app/api/protected/route.ts" has an invalid export:
  "unknown" is not a valid POST return type:
    Expected "void | Response | Promise<void | Response>", got "unknown".

@SongDerrick
Copy link
Author

SongDerrick commented Aug 31, 2024

@ThangHuuVu It runs into next build type errors. checkout this issue #11728

@balazsorban44
Copy link
Member

balazsorban44 commented Sep 4, 2024

This rather sounds like a bug. We don't want to recommend as any as the solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants