fix(next): correctly parse headers with RSC

[balazsorban44]

We weren't correctly parsing headers and it caused issues when deployed.

Also, authOptions is not required anymore

- import { authOptions } from "pages/api/auth/[...nextauth]"

export default async function Page() {
-  const session = await unstable_getServerSession(authOptions)
+  const session = await unstable_getServerSession()
...
}

☕️ Reasoning

🧢 Checklist

• Documentation
• Tests
• Ready to be merged

🎫 Affected issues

Please scout and link issues that might be solved by this PR.

Fixes: INSERT_ISSUE_LINK_HERE

📌 Resources

• Security guidelines
• Contributing guidelines
• Code of conduct
• Contributing to Open Source

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Updated
next-auth	⬜️ Ignored (Inspect)		Nov 7, 2022 at 8:16PM (UTC)

[github-actions]

🎉 Experimental release published 📦️ on npm!

pnpm add next-auth@0.0.0-pr.5753.2b78e705

yarn add next-auth@0.0.0-pr.5753.2b78e705

npm i next-auth@0.0.0-pr.5753.2b78e705