1(self.webpackChunk_N_E=self.webpackChunk_N_E||[]).push([[189],{7275:function(e,s,i){(window.__NEXT_P=window.__NEXT_P||[]).push(["/client-redirect",function(){return i(5813)}])},5813:function(e,s,i){"use strict";i.r(s);var n=i(5893),t=i(1261),a=i(3299),o=i(1163);s.default=()=>{var e;let s=(0,o.useRouter)(),{status:i,data:r}=(0,a.useSession)({required:!0,onUnauthenticated(){s.push("/","/",{})}});return"loading"===i?"Loading or not authenticated...":(0,n.jsx)(n.Fragment,{children:(0,n.jsxs)(t.Z,{children:[(0,n.jsx)("div",{children:(0,n.jsxs)("h1",{children:["Hello, ","".concat(null!==(e=r.user.name)&&void 0!==e?e:r.user.email)," This is a protected route. You can see it because you're logged in."]})}),"Client Side Rendering This page uses the useSession() React Hook. The useSession() React Hook is easy to use and allows pages to render very quickly. The advantage of this approach is that session state is shared between pages by using the Provider in _app.js so that navigation between pages using useSession() is very fast. The disadvantage of useSession() is that it requires client side JavaScript.",(0,n.jsxs)("blockquote",{children:[(0,n.jsx)("p",{children:"This page is protected using the useSession hook."}),(0,n.jsx)("p",{children:"Either way works."}),(0,n.jsxs)("p",{children:["But in this case the session is ",(0,n.jsx)("strong",{children:"not"})," available on the first render."]})]})]})})}}},function(e){e.O(0,[664,261,774,888,179],function(){return e(e.s=7275)}),_N_E=e.O()}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.