This is awesome, I will try the steps you mentioned. Will ask if I need anymore help. Thanks

Sure!

Getting a lot of type errors, I imported stuff in the function from lib/build like how the ThirdPartyEmailPasswordRaw is imported

Can you show me a few examples of the kinds of errors?

Argument of type 'import("/home/ankitjey/Desktop/sideprojects/unnamed-backend/node_modules/supertokens-node/lib/build/recipe/thirdpartyemailpassword/recipe").default' is not assignable to parameter of type 'import("/home/ankitjey/Desktop/sideprojects/unnamed-backend/node_modules/supertokens-node/lib/build/recipe/emailpassword/recipe").default'. The types of 'config.sessionFeature.setJwtPayload' are incompatible between these types. Type 'import("/home/ankitjey/Desktop/sideprojects/unnamed-backend/node_modules/supertokens-node/lib/build/recipe/thirdpartyemailpassword/types").TypeInputSetJwtPayloadForSession' is not assignable to type 'import("/home/ankitjey/Desktop/sideprojects/unnamed-backend/node_modules/supertokens-node/lib/build/recipe/emailpassword/types").TypeInputSetJwtPayloadForSession'. Types of parameters 'context' and 'formFields' are incompatible. Type 'TypeFormField[]' is not assignable to type 'TypeContextThirdParty | TypeContextEmailPasswordSessionDataAndJWT'. Type 'TypeFormField[]' is missing the following properties from type 'TypeContextEmailPasswordSessionDataAndJWT': loginType, formFieldsts(2345)

const formFields: { id: string; value: string; }[] Argument of type '{ id: string; value: string; }[]' is not assignable to parameter of type 'TypeContextEmailPasswordSignUp | TypeContextThirdParty'. Type '{ id: string; value: string; }[]' is missing the following properties from type 'TypeContextThirdParty': loginType, thirdPartyAuthCodeResponsets(2345)

Oh yea.. one min

So change the assignment of

recipeInstance

to:

js
app.post("/auth/signup", async (req, res) => {

  let recipeInstance = ThirdPartyEmailPasswordRaw.getInstanceOrThrowError().emailPasswordRecipe;

  // TODO: This will handle sign up requests from email password login. The body for this can be found here: https://github.com/supertokens/supertokens-node/blob/master/lib/ts/recipe/emailpassword/api/signup.ts
})

app.post("/auth/signinup", async (req, res) => {

    let recipeInstance = ThirdPartyEmailPasswordRaw.getInstanceOrThrowError().thirdPartyRecipe;

  // TODO: This will handle sign up and in requests from social login. The body for this can be found here: https://github.com/supertokens/supertokens-node/blob/master/lib/ts/recipe/thirdparty/api/signinup.ts
})

Basically added

.emailPasswordRecipe

and

.thirdPartyRecipe

.

I think after this, the type errors should go away

Wow it worked

okay nice! haha

can I use

localhost

for the

websiteDomain

while testing?

Yeah you can

awesome! 🙌

Yes. But also keep in mind that implies that the port is

80

by default

cool, good to know!

const recipeInstance: Recipe | undefined
Object is possibly 'undefined'

Getting this for the signinup code

You can just have a check below it checking if it's undefined. If it is, throw an error to the client

since it should never be undefined given that you have added social providers

wow this is insane!

I literally spent 5min of copy-pasting React stuff and now I can see the auth page...

so, at this point I should consider the frontend auth already set up? 🤔

if that's true, then ST is just magical. 🪄 🔮

Well with that done you already can register and login users, now you have to just create the session and keep tracking on them, well if you want to do it

I guess I want to. isn't that the whole idea behind the sessions - to keep track of whether they are logged in or not, right?

Yes

awesome! 🙌

btw, isn't the session management also set up when configuring the backend auth part? or is it a separate step?

https://supertokens.io/docs/thirdpartyemailpassword/quick-setup/backend over there you can see its a session verification