mirror of
https://github.com/SrIzan10/next-auth.git
synced 2026-05-01 10:55:20 +00:00
5c1826a8d1
* docs: add Gatsby example, move Next.js example * chore: fix sync action * docs(example): fix README link
45 lines
1.4 KiB
TypeScript
45 lines
1.4 KiB
TypeScript
import { useSession, getSession } from "next-auth/react"
|
|
import Layout from "../components/layout"
|
|
import type { NextPageContext } from "next"
|
|
|
|
export default function ServerSidePage() {
|
|
// As this page uses Server Side Rendering, the `session` will be already
|
|
// populated on render without needing to go through a loading stage.
|
|
// This is possible because of the shared context configured in `_app.js` that
|
|
// is used by `useSession()`.
|
|
const { data: session, status } = useSession()
|
|
const loading = status === "loading"
|
|
|
|
return (
|
|
<Layout>
|
|
<h1>Server Side Rendering</h1>
|
|
<p>
|
|
This page uses the universal <strong>getSession()</strong> method in{" "}
|
|
<strong>getServerSideProps()</strong>.
|
|
</p>
|
|
<p>
|
|
Using <strong>getSession()</strong> in{" "}
|
|
<strong>getServerSideProps()</strong> is the recommended approach if you
|
|
need to support Server Side Rendering with authentication.
|
|
</p>
|
|
<p>
|
|
The advantage of Server Side Rendering is this page does not require
|
|
client side JavaScript.
|
|
</p>
|
|
<p>
|
|
The disadvantage of Server Side Rendering is that this page is slower to
|
|
render.
|
|
</p>
|
|
</Layout>
|
|
)
|
|
}
|
|
|
|
// Export the `session` prop to use sessions with Server Side Rendering
|
|
export async function getServerSideProps(context: NextPageContext) {
|
|
return {
|
|
props: {
|
|
session: await getSession(context),
|
|
},
|
|
}
|
|
}
|