Hey @User, we decided to go with only express, so no need to prioritise making flask one work with express, you can prioritise other things if needed, thanks.

@User thanks for letting me know. So will you be using supertokens with express then?

Yes.

sounds good!

Also, I'm using typescript with express and I'm trying to load

connectionURI

from

process.env.SUPERTOKENS_URI

, it looks like the type for it is

string | undefined

, and type for

connectionURI

is string, so I'm unable to assign this, is there a workaround for this other than adding

// @ts-ignore

above it?

So this is a conscious design decision from our side so that it doesn't get missed from the user. What you can do is something like:

ts
let connectionURI: string | undefined = process.env.SUPERTOKENS_URI;

if (connectionURI === undefined) {
  throw new Error("Please provide the SuperTokens connectionURI");
}

supertokens.init({...})

This way, I think TS will stop throwing the error.

Hahah, just did that

hahahaha

👍

Oh actually wait

I did this

const connectionURI = process.env.SUPERTOKENS_URI || "https://try.supertokens.io";

But I think your solution is safer one.

technically, that works, but

try.supertokens.io

is not meant for any production use. It's only meant for trying out supertokens quickly. So I would still prefer to throw an error or something in case

process.env.SUPERTOKENS_URI

is

undefined

Yeah, correct.

Thanks.

Also, I edited the code snippt above to throw an error in the IF statement

Okay cool, thanks.

We can use const right? any reason for using let?

yea const works. I'm just used to using

let

instead

Ah okay cool, thanks.

Hey rp, so I'm trying to use supertokens with next following this guide - https://supertokens.io/docs/emailpassword/nextjs/supertokens-with-nextjs, but I'm using typescript and in step 2 ,

EmailPassword.init()

and

Session.init()

are causing error saying

An argument for 'config' was not provided.

, I think you have to make config argument optional in type definition? I'm new to typescript, can you please suggest a solution? Thanks.

hey @User thanks for pointing it out

Fixing it now. Should be available in 10-15 mins

@User I have released version 0.2.2 with the typescript fix. Please lmk if the error still persists. Thanks

Sure, thanks.

hey @User you should update supertokens-node to

3.2.1

. It has a few important fixes

thanks

Sure, thanks for the heads up.

Hey there came across Supertokens while trying to implement an auth flow with faunadb + third party auth(outseta)+ nextjs After a user login in i pass a JWT to the an endpoint where i validate and issue a faunadb access token for that user. i'm wondering how to go about using superTokens to manage the session of that user? is it possible to use the supertoken with faunaDB feature standalone?