yeah!

so if process is not defined, then

process !== undefined

should be false and other conditions should not be checked..

we applied

const process = process || undefined;

and it was working!

hmmmm.. interesting.

can you print out the value of

process

before

const process = process || undefined;

?

same thing!

I see.

I know what the issue is..

will released a fix in 20-30 mins..

thanks for pointing this out

sure thanks!

@User , i have released a new version for supertokens-website v8.1.1 which should have the fix.. lmk if the error still persists 🙂

Hey guys, thank you for SuperTokens! I'm trying to evaluate if SuperTokens could be a good fit to migrate from Auth0. We want to migrate mainly because the local development experience of Auth0 is awful, you just can't run it locally. (+ their lack of discord or slack community is very frustrating) So my main requirements are to be able to : - 1 / run the authentication service locally for dev and self-hosted for staging - 2 / update the JWT with the user's roles, both at the token creation time and later (eg. when we let the user chose the identity he wants for its current session, when a user has many identities linked to its account (eg. 1 user account -> 3 identities in 3 companies as employee, and 1 identity as manager)) - 3 / synchronize users that have been created upfront by the backend (eg. when inviting a team member, or user) with the user created when he signs up 1 / this seems OK 2 / I read the doc and found a way to do both 3 / It's not clear if the SuperTokens (when self-hosted) DB/schema is separate from my main DB where I store my users and main data model? Can they be the same DB? Or do SuperTokens needs an isolated DB/schema? If this is the case how can I synchronize new supertokens users (signup) with the users I provisioned upfront in my own main DB? If SuperTokens can run on my own main DB/schema (ie. I only have one user table then) how can it work when I use the hosted version of SuperTokens? Thank you so much!

Hey @dr_goodcall. You should keep supertokens tables separate from your tables. On sign up, we insert the user’s userId, email and timeJoined into our table (plus third party info if they used that to login)

You can add post sign up logic to insert any other info that you may want to associate with the user in your own table

If there is no other info against a user, then you don’t need to do anything post sign up.

You can tell supertokens to create its tables in the same db as your other tables. Not an issue

If you use the hosted version of supertokens, AND you have some other user metadata to store, then you will need to create your own table in your own db to store that meta data

However, if you don’t have additional meta data, then you don’t need to create the extra. You can query supertokens to get info for any user or paginate across all users.

Hi guys, what is the best way to change language in sign in/up form? Supertokens.init is called before the language is fetched, so I can't provide it in formFields config.

Is your language dynamically chosen?

@User ^

yes

hmmmm

At the moment, the best way would be to directly change it using JS.. via dom manipulaiton

we have an open issue for this: https://github.com/supertokens/supertokens-auth-react/issues/233

An alternate method is to disable the default implementation and copy / paste the theme code from the auth-react repo into your own repo and modify that. This is equivalent to a "swizzle" if you are familiar with that concept.

It's explained in the issue itself.

thanks, I'll look into it!