Hi! I've implemented the SuperTokens login to a vue3 project and it works beautifully, but am greeted with lint-like errors for every class across the app, and I've isolated it down to the

supertokens-auth-react

package that appears to be causing it. Any info or advice to clean these errors would be super helpful 😊 Additionally here is the inline error

Type '{ class: string; }' is not assignable to type 'DetailedHTMLProps<HTMLAttributes<HTMLDivElement>, HTMLDivElement>'.
  Object literal may only specify known properties, and 'class' does not exist in type 'DetailedHTMLProps<HTMLAttributes<HTMLDivElement>, HTMLDivElement>'.ts(2322)
index.d.ts(3176, 13): The expected type comes from property 'div' which is declared here on type 'IntrinsicElements'

Hi! I was interested in using Supertokens for a side project. Right now, my strategy is to use the pre-built UI to accelerate setting up the app and then switch to a custom auth UI down the road. Is this an easy switch to make?

Hi, hope you all are fine ! I got

{
message: "try refresh token"
}

on the

/auth/dashboard

Hi! I'm trying to test the Passwordless (SuperTokens 4.2) recipe on Postman, but I get a 400 response: "Please provide exactly one of email or phoneNumber". I've followed the example on https://supertokens.com/docs/passwordless/testing/testing-with-postman. What could I be doing wrong?

Hi, I'm looking to implement "web3" authentication. Is there anything like that integrating with SuperTokens already? If not, I would appreciate any pointers to the best way for me to implement it myself. (By "web3" auth, this is what I mean: on a new session the server sends a challenge to the user client who signs it with their crypto wallet and sends back to the server. The server compares the signed challenge with the previously registered public keys for the user. Here's an in-depth "vanilla" integration example https://www.toptal.com/ethereum/one-click-login-flows-a-metamask-tutorial)

how to use thirdpartyemailpassword in tauri/sveltekit?

Hey, I'm trying to setup Apollo graphql + Nest.js by following the guide, and I manage to get the session info on a controller using the Auth guard and Session param decorator (from the guide) but not on a resolver. I tried (with inspiration from the graphql integration guide) to use a CanActivate guard and access the session with

GqlExecutionContext.create(context)

and also tried injecting the session param to the resolver with

export const User = createParamDecorator(
  (data: unknown, ctx: ExecutionContext) => {
    const x = GqlExecutionContext.create(ctx);
    const context = x.getContext();
    return context.session;
  },
);

with no success and couldn't find any code example that combines graphql + nest

Hey, when setting custom claims in the access token where is the best place to do that? Using refreshPOST override, or make it a side effect in an api call which is called by the frontend as part of the login process? I've been reading through the docs and I can see a few examples of doing it for a /login route but just struggling to understand is that overriding a login route provided ootb by supertokens or is it in addition to the normal flows?

I'm thinking it could have something to do with express 4. To set headers in express 4: res.set(key,value). But looking at this it seems it tries setting the header with methods res.header and res.setHeader. https://github.com/supertokens/supertokens-node/blob/master/lib/ts/framework/utils.ts

hey guys, we are a little lost implementing auth for our capacitor apps (different domains)... What's the usecase for the cookieHandler?

js
  supertokens.init({
    ...frontendConfig().appInfo,
    cookieHandler: capacitorCookieHandler,
  })

We are following this guide now, since our implementation didn't work as expected (due to lax cookies & safari webkit issue): https://supertokens.com/docs/thirdpartyemailpassword/advanced-customizations/examples/localstorage/about