Would the best way to implement sessions with supertoken be to send the supertoken(that we usually send using cookies) in the header of socketio requests, or does a better way exist?

Hi 🙂 New to Supertokens (but extensively used to Auth0); I'm trying to implement a "universal-login"-like solution with Supertokens. Is there something straightforward ? My idea was launching a core, a node backend and a frontend dedicated for this (on a separate domain, say identify.example.com). I'm afraid of the interactions with the actual end application, which will rely on another domain. Any thoughts / references ?

Hello, The gist is, I'm hoping someone can give me a tip on how to check whether the /auth/signinup api call has completed. Here's the context: I'm using third party login, and I overrode the thirdPartySignInUpPOST api to add logic to check whether a user with the given supertokens userId exists in my app's database. If no such user exists, it creates one. I refer to this api call as /auth/signinup. I'm wondering if there is a way for me to check whether /auth/signinup has completed, because I have another call, /api/getUserData/, that I want to happen on login, to fetch user data, which as of now depends on the user data having been initialized in /auth/signinup. I tried using Session.doesSessionExist to trigger my api call, but it appears that the session comes into existence before /auth/signinup has completed, because using doesSessionExist as a trigger results in this order of calls: OPTIONS /auth/authorisationurl?thirdPartyId=google 204 GET /auth/authorisationurl?thirdPartyId=google 304 OPTIONS /auth/signinup 204 OPTIONS /api/getUserData 204 POST /api/getUserData 401 POST /auth/signinup 200 Any insight would be appreciated.

I think I've found a bug in the interaction between Next.js's

basePath

and SuperTokens' `apiBasePath`: If you set a

basePath

, the

req.url

which the app sees doesn't include the prefix. As such, your prefix check fails to match (https://github.com/supertokens/supertokens-node/blob/a7dcb2b4123c512de63d5d5206da315a679759be/lib/ts/supertokens.ts#L344) and the middleware is not employed. At the same time, it seems I need to include Next.js's

basePath

as part of the

apiBasePath

otherwise the generated URLs are missing it and Next can't route the request properly.

Hey all, so I'm working on a

next

and

expo

universal app. Basically the concept is that the same app runs on

nextjs

and

react native

. Truly write once and have

80%

code usage across both your app and your website. Long story short auth is often the hardest part of getting this stack working. This week I went down the rabbit hole and wrote a single

supertokens

client that can be shared between both

react native

and

nextjs

. Only thing left to figure out is a token refresh strategy. Anyways, I was curious if anyone in the community was interested in the code or if the supertokens core team (@rp_st) wanted to do a PR on the

t3-turbo

(https://github.com/t3-oss/create-t3-turbo) repo or the

create-universal-app

(https://github.com/chen-rn/CUA) repo as these communities are dying to have a cross platform open source way to do auth. I've got the code packaged up, a 10 min video overview made, and it is ready to share... I'm just massively burnt out from OSS and I believe supertokens has the best financial incentive to maintain the codebase. Feel free to DM me if interested.

Hi, does any one know why I'm getting this error when I add to the config file EmailPassword.init():

api/node_modules/supertokens-node/lib/build/recipe/emailverification/index.js:169
Wrapper.init = recipe_1.default.init;
                                ^
TypeError: Cannot read properties of undefined (reading 'init')

Thanks

any support for sveltekit? with components like etc?

Hello. I am trying to implement the user dashboard but I am getting a blank white page. It looks like the html and scrips are all being downloaded and there are no errors in the console. Not quite sure where to go from here. I am using aws lambda for hosting along with a reverse proxy so could this be caused by a mismatch in settings?

Hey guys, thanks for the amazing tool ❤️ I was checking the pricing for SuperTokens and Auth0, and I think that I misunderstood the pricing system of one of them 😅 On the SuperTokens website, looks like that SuperTokens is the cheapest one, but if they charge 2 cents / MAU after you reach the 5k limit, you would have to pay $100, right? But at Auth0, you have a 7k MAU free limit, and after that, you pay $23 per month to have 10k MAU. Am I misunderstanding something?

Hi is it possible to disable the reset password and signup and do this via APIs only?