ITEnthusiasm
04/10/2024, 9:34 PMThirdPartyEmailPassword
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.)rp_st
04/11/2024, 4:24 AMITEnthusiasm
04/11/2024, 12:54 PMrp_st
04/11/2024, 2:18 PMITEnthusiasm
04/11/2024, 3:21 PMsupertokens-node
again too when I find the time. I just don't have said time at the moment. 😬rp_st
04/11/2024, 3:22 PM