You should connect the core instance to a postgres / mysql instance.

ok

is express router compatible with supertokens middleware?

Yes.

@User Hey, im using a Next.js for frontend and have followed steps so far, but what i do not get is why is backend also a part of the nextjs? my api is running on another server and its where i put supertokens installation also as i'd like to protect routes / use supertokens in other api things what do you recommend, is using just normal react recipe in next ok?

Yes. Since your backend is independent to NextJS, you can ignore the backend setup in the NextJS docs.

ok, thanks man 👍

Hi everyone ! My custom function

signInUpPOST

is not called when I sign in with Google or Facebook. I followed this implementation: https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/signup-form/built-in-providers#get-the-third-party-providers-access-token Is it an existing issue ?

Hi @User, I can't find an issue like that. Could you please share your code?

Just a helpful Next.js/Vercel protip for anyone who spent the last 48 hours perplexed by something very VERY trivial🙄 : Vercel's new environment variable setup does not require quotations for some URL vars. I began working with Supertokens early in the spring, and had a demo set up, running fine. I had my URL variables set, with quotes, using secrets only (how silly!). I recently ran some npm updates, and was stuck with a blank screen, no redirection to /auth, etc. -- had no idea what the issue was. tl;dr; creating a fresh project and troubleshooting this issue got me back where I needed to be, ready for launch. Hope this saves someone else a few headaches.. Also, much love to the Supertokens team! Glad to see the progress (and node.js support!) going on over the Summer.

Thank you @theefunklord 👍. A quick question: this applies just to users of vercel? Or to all NextJS users?

Hey @rp! I am using both Next (project based on the with-supertokens-app example, EmailPassword recipe), and Vercel

I see. So if using double quotes, does that mean the double quotes gets inserted as part of the secret string?

I believe so. At least it appears to be that way with my older deployments/project. When reverting back to earlier versions of Supertokens in that older project, those secrets with quotes seem to work fine. I can see a 1:1 with my new project (no secret, no quotes), and the old project (with secrets, with quotes) on my different domains.

ohh. So does this mean that earlier putting quotes in the value of

websiteDomain

or

apiDomain

worked fine, but now it doesn't?

You can find my code here https://gist.github.com/mpicciolli/909d8d236ea1ad34dd8472046146d264

I see. Do you add the middleware and errorHandlers somewhere?

@User I cloned this repository to verify if I have the same issue with your code. And yes I have issue even if I add the middleware and errorHandlers

I just ran the above via the demo app, and it does print out the

response.authCodeResponse

as expected. Here is my code (same as your code more or less..)

I am using supertokens-node version 7.1.0 (but this should also work in previous versions). Which version are you using?

@User Problem solved. My bad guys. Thank you

Great! What was the error? Just curiosity.. cause the code you shared seemed all fine.

Hi, I am building a deno app and I'd like to use supertokens. Can I use the node api in deno?

I don’t know if node is 100% compatible with Deno. If it is, you should be able to use it.

How to build from source and install?

Note that the above will work only on linux / mac based systems. You might run into issues in windows

Let me list here the problems I face in following from that link you shared.

please do.

1. Looks like I need to clone the supertokens-root repo first and run the "loadModules" first... that gets me the "supertokens-core" and "cloning "supertokens-plugin-interface and "utils" repos. 2. "./startTestingEnv --wait" gets completed successfully... 3. "./startTestingEnv" runs successfully. No tests failed. 400 odd tests are all PASSED. 4. "java -classpath "./cli/*" io.supertokens.cli.Main true install" requires lot of hacks. "./cli/*" does not have the expected jar. It is under "./cli/jar". Somewhere it complained about version.yaml not existing. Hacked it by copying version.yaml from docker machine... After fixing all the classpath problem, "supertokens list" works fine. But, "supertokens start" failed...