Never been this exited about auth before 😅

hehe! 😆

Hey again! So I deployed my next app from your template now and set both the

NEXT_PUBLIC_APP_URL

and

APP_URL

vars but I still get redirected to localhost. From the config file I put a console.log just to make sure:

js
const websiteDomain =
  process.env.APP_URL ||
  process.env.NEXT_PUBLIC_APP_URL ||
  `http://localhost:${port}`;
console.log('websiteDomain', websiteDomain);

and it logs the correct url. Any ideas?

You get redirected from where?

Sorry, from here:

that's strange.

Can you instead change the websiteDomain to that value you want (instead of using env vars?)

and check if the same thing is happening or not

🤯 that worked, so weird

or maybe not I realise now, need to inject the env vars into the build step

Yes! That’s exactly what you need to do 🙂

Thank you! Always forget this on new projects..

Having a small typescript issue. My backend config looks like:

ts
export let backendConfig = () => {
  return {
    framework: 'express',

But then when I use it with

SuperTokensNode.init(SuperTokensConfig.backendConfig())

it says > Type 'string' is not assignable to type 'TypeFramework'. Diving into

TypeFramework

shows me it should be fine:

export declare type TypeFramework = "express" | "fastify" | "hapi" | "loopback" | "koa" | "awsLambda";

Then I thought I need to define the return type of

backendConfig

so I imported it like this:

import { TypeFramework } from 'supertokens-node/lib/build/framework/types';

but then I get > ... is not assignable to type '"awsLambda"' I will just ts-ignore it for now, but thought I would mention it. Let me know if I should report an issue somewhere

You could create an issue in the supertokens-node repo please 🙂

Upgraded all packages and solved this one btw

ah right! okay!

@User I think you had some question about getting the default user Id from the session context - that happens if you don't wrap your components with the auth provider component we have. Did you already manage to solve this issue (since you deleted that message)?

Sorry mate, I've been rubberducking like crazy here 😅

haha! Don't worry about it 🙂

feel free to ask stuff.

I ended up with this wrapper, the only problem is this gives me a warning because the SSR HTML doesn't match what the client renders. If I don't do this I never get any data from

useSessionContext

without losing SSR

Have you tried doing something like this instead?

js

import dynamic from 'next/dynamic'
import ThirdPartyEmailPassword from 'supertokens-auth-react/recipe/thirdpartyemailpassword'

const ThirdPartyEmailPasswordAuthNoSSR = dynamic(
  new Promise((res) =>
    res(ThirdPartyEmailPassword.ThirdPartyEmailPasswordAuth)
  ),
  { ssr: false }
)

export default function Home() {
  return (
    // we protect ProtectedPage by wrapping it
    // with ThirdPartyEmailPasswordAuthNoSSR

    <ThirdPartyEmailPasswordAuthNoSSR>
      <ProtectedPage />
    </ThirdPartyEmailPasswordAuthNoSSR>
  )
}

It's a code snippet from here: https://supertokens.io/docs/thirdpartyemailpassword/nextjs/protecting-route

this will make sure that

ThirdPartyEmailPasswordAuthNoSSR

only runs on the client side, and never during SSR

Yeah, I started with that, but I want to keep SSR. I guess because

ThirdPartyEmailPasswordAuth

has an extra div somewhere it gives me this misrender. I might dive into it later

Hmm. I don't think

ThirdPartyEmailPasswordAuth

is made with SSR in mind. I'm surprised that it doesn't throw an error..

But in your code, you are doing

typeof window !== 'undefined'

which means that you only want to use it on the client side

Yes, to avoid that thrown error 😁

So then why not use the

dynamic

feature provided by next?