Hey @rp_st I have intergrated user login using google, On frontend how I can get the user information after login, like userId?

https://discord.com/channels/603466164219281420/907932061669654548/1202007865028775937 I've started the migration from the Remix example to the Next.js app directory example. (At least for now.) And I think Remix does things way better. 😅 I wanted to suggest adding documentation on how to use the

ThirdPartyEmailPassword

option without using the Express middleware, and perhaps suggest exposing clear functions for it if they aren't yet available. (I assumed that they would be available since we now have things like

*withoutRequestResponse()

.) I've been approached multiple times on both my Remix and my SvelteKit examples regarding how to get

ThirdPartyEmailPassword

up and running. It seems to be the most common recipe (or one of the most common). And having a way to set things up clearly (without having to bring other SuperTokens packages into the mix) would likely be a big win. It might also alleviate some of the package management that SuperTokens has to deal with for various JS frameworks. I would look into it, but I unfortunately haven't had the time to scrutinize SuperTokens's internals like I did last time. 😅 I'm still looking for an opportunity. I'm only just now getting to the Next.js app dir example. (I know SuperTokens has one. This would just be one that would be more direct -- requiring less NPM packages and higher order functions.)

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?

Can supertokens be used with a persistent sqlite db file, instead of postgresql?

I am testing a service using a hosted production supertokens using a valid sms key, and I need to perform OTP sign in many times. However all of a sudden I stopped receiving sms messages and there are no logs in the console. I am wondering if this could be due to some default spam detection or if this could be due to some rate limiting against my phone number?

Hello, I am trying to break my overrides out to be more modular, but I am having trouble typing them.

ts
import { db } from '@db/index';
import { users, profiles } from '@db/schema';

const thirdPartySignInUpOverride =
  (originalImplementation) => async (input) => {
    let response = await originalImplementation.thirdPartySignInUp(input);

    if (response.status === 'OK') {
      let { id, emails } = response.user;
      console.log('USER SIGNED UP', id);
      await db.transaction(async (trx) => {
        await trx.insert(users).values({
          id,
          email: emails[0],
        });
        await trx.insert(profiles).values({
          userId: id,
        });
      });

      // This is the response from the OAuth 2 provider that contains their tokens or user info.
      let providerAccessToken = response.oAuthTokens['access_token'];
      let firstName =
        response.rawUserInfoFromProvider.fromUserInfoAPI!['first_name'];

      if (
        response.createdNewRecipeUser &&
        response.user.loginMethods.length === 1
      ) {
        // TODO: Post sign up logic
      } else {
        // TODO: Post sign in logic
      }
    }
    return response;
  };

export default thirdPartySignInUpOverride;

I am really not sure of what the

originalImplementation

type should be. I have tried creating an interface from ThirdPartyPasswordless recipe, but that didn't work at all. Any ideas? Edit: Found a way to type using RecipeInterface. Not sure if this is documented? I had to search in discord and got lucky

Hi, is there a way to mount the dashboard endpoint to a separate port with a seperate domain and gateway settings? except the obvious way of creating a separate deployment of our BE service for that purpose?

Hi. I have a question regarding the mysql database setup. According to the documentation [1], creating tables "happens automatically, unless you provide a MySQL user that doesn't have table creation permission". - Is it advised to give the mysql user table creation permissions? - How does SuperTokens deal with database migrations? E.g. if a new version of supertokens-core requires a new table, how will this table be added? Is this done automatically? If so, what if the MySQL user doesn't have table creation permission? [1]: https://supertokens.com/docs/session/quick-setup/database-setup/mysql

Hey everyone, I'm facing an issue with my Express backend setup along with Supertokens for session management. Here's a snippet of my backend code:

javascript
import express from "express";
import { verifySession } from "supertokens-node/recipe/session/framework/express";
import { SessionRequest } from "supertokens-node/framework/express";

let app = express();

app.post("/like-comment", verifySession(), (req: SessionRequest, res) => {
    let userId = req.session!.getUserId();
    //....
});

I've added

verifySession()

to ensure that only authenticated users can access the

/like-comment

route. However, I'm having trouble accessing this route from the front-end using Axios. I've wrapped my component inside

SessionAuth

so that logged-in users have access, but I keep receiving a 401 error. Could anyone guide me on how to properly access this route from the front-end using Axios and ensure that the user is authenticated? Thanks in advance!

@rp_st Getting this error on trying to login : { "statusCode": 500, "message": "SuperTokens core threw an error for a GET request to path: '/public/users/by-accountinfo' with status code: 504 and message: \r\n504 Gateway Time-out\r\n\r\n504 Gateway Time-out\r\n\r\n\r\n", "timestamp": "2024-01-19T07:46:59.841Z" }