Has anyone found that when they're logged in with super tokens and the backend is verifying their ID, that after they move off the frontend tab for a bit and come back, the userId is rendered as null on the backend? But then when the frontend is refreshed, the userId is correctly set again

This is one of our components. We have multiple routes. My understanding was that in the if (sessionContext.loading === true) { return null; } if we changed the return null to a loader component, then we could display a loader between our routes but we are unable to see anything even when the route takes time to load. Is there a different way to show loaders?

Hi! One question please: what would be the best implementation for a user with "teacher" role, that wants to create emailpassword users with the role "student" in a customize signup page?

How to override default styling that has !important on it in the prebuilt UI? The Google Icon has an extra margin left for some reason

hi, @rp_st We encountered this error when we tried to log in. But we did not make any changes to supertokens that would affect this. why could this be? SuperTokens core threw an error for a request to path: '/public/recipe/signin' with status code: 403 and message: Email password login not enabled for tenant.

Hello. I've been using the ThirdPartyEmailPassword recipe for my Supertokens setup on the backend and everything worked great. Now I actually wanted to switch to ThirdParty recipe, since I'm not really doing email password login currently in my app. But after switching the backend config to use ThirdParty recipe, the

/{apiBasePath}/signinup

route is no longer there and I can not POST to it. Can anyone suggest what could be the cause? Thanks.

Hello, Why can't I import the ui in react

import { getSuperTokensRoutesForReactRouterDom } from "supertokens-auth-react"

It tells me that it can't find a module with that name. Framework : React Vitejs Typescript Additional information: without vitejs, using create-react-app everything works perfectly.

SuperTokens is officialy not compatible with Deno, right? Now that Deno added support for npm packages, im wondering: Did anyone get Supertokens to work with deno?

@rp_st Can you help me please with this 'SuperTokens - Exception during pool initialization'?

In accessTokenAPIResponse I only get access_token, token_type, expires_in, refresh_token and scopre :/