603466164219281420 #support-questions

javascript
  SuperTokensNode.init({
    supertokens: {
      connectionURI: process.env.SUPERTOKENS_DOMAIN,
      apiKey: process.env.SUPERTOKENS_API_KEY,
    },
    appInfo: {
      appName: "storefront",
      apiDomain: websiteDomain,
      websiteDomain,
      apiBasePath,
    },
    recipeList: [
      ThirdPartyEmailPasswordNode.init({
        signUpFeature: {
          handlePostSignUp: async (user, context) => {
            const { id, email } = user
            //isBrowser() && (await fetchApi("/api/users/create", { id, email }))
          },
        },
        providers: [],
      }),
      SessionNode.init(),
    ],
  })

othiagocruz

03/30/2021, 2:21 PM

could be the providers i guess

othiagocruz

03/30/2021, 2:24 PM

it does complete the sign up process tho

03/30/2021, 2:25 PM

what's the value of websiteDomain and apiBasePath?

othiagocruz

03/30/2021, 2:25 PM

it doesnt actually

othiagocruz

03/30/2021, 2:25 PM

its

03/30/2021, 2:25 PM

cause this error doesn't seem to be related to

handlePostSignUp

othiagocruz

03/30/2021, 2:25 PM

"http://localhost:3000"

03/30/2021, 2:26 PM

and for apiBasePath?

othiagocruz

03/30/2021, 2:26 PM

const apiBasePath = "/api/auth/"

03/30/2021, 2:27 PM

if you remove the

handlePostSignUp

, does that error go away?

othiagocruz

03/30/2021, 2:30 PM

uhh no

othiagocruz

03/30/2021, 2:30 PM

😅

03/30/2021, 2:31 PM

can you show me the full stack trace of the error?

othiagocruz

03/30/2021, 2:31 PM

i think i know what it is hold on

othiagocruz

03/30/2021, 2:33 PM

nope, still getting the same error, this is weird it was working a few steps ago

othiagocruz

03/30/2021, 2:33 PM

Copy code

TypeError: Only absolute URLs are supported
    at getNodeRequestOptions (C:\offscript\storefront\node_modules\node-fetch\lib\index.js:1305:9)
    at C:\offscript\storefront\node_modules\node-fetch\lib\index.js:1410:19
    at new Promise (<anonymous>)
    at fetch (C:\offscript\storefront\node_modules\node-fetch\lib\index.js:1407:9)
    at fetchApi (C:\offscript\storefront\.next\server\pages\_app.js:5511:21)
    at Object.handlePostSignUp (C:\offscript\storefront\.next\server\pages\_app.js:7066:76)
    at Recipe.<anonymous> (C:\offscript\storefront\node_modules\supertokens-node\lib\build\recipe\thirdpartyemailpassword\recipe.js:285:68)
    at Generator.next (<anonymous>)
    at C:\offscript\storefront\node_modules\supertokens-node\lib\build\recipe\thirdpartyemailpassword\recipe.js:30:75
    at new Promise (<anonymous>)
    at __awaiter (C:\offscript\storefront\node_modules\supertokens-node\lib\build\recipe\thirdpartyemailpassword\recipe.js:12:16)
    at Object.handleCustomFormFieldsPostSignUp (C:\offscript\storefront\node_modules\supertokens-node\lib\build\recipe\thirdpartyemailpassword\recipe.js:284:25)
    at Object.<anonymous> (C:\offscript\storefront\node_modules\supertokens-node\lib\build\recipe\emailpassword\api\signup.js:67:51)
    at Generator.next (<anonymous>)
    at fulfilled (C:\offscript\storefront\node_modules\supertokens-node\lib\build\recipe\emailpassword\api\signup.js:29:36)
    at runMicrotasks (<anonymous>)

othiagocruz

03/30/2021, 2:33 PM

this is the stack

03/30/2021, 2:39 PM

What's the value of

process.env.SUPERTOKENS_DOMAIN,

othiagocruz

03/30/2021, 2:41 PM

https://8cfce9e1870a11ebbcb07d0af03fd0dc-eu-west-1.aws.supertokens.io:3567

03/30/2021, 2:41 PM

Sure?

03/30/2021, 2:42 PM

Cause the error seems to come from when querying the core.. which means something is wrong with the URL being queried

othiagocruz

03/30/2021, 2:42 PM

oh this is weird, i will verify

03/30/2021, 2:43 PM

Also, can you please tell me which version of supertokens-node is being used?

othiagocruz

03/30/2021, 2:43 PM

"supertokens-node": "^4.1.3",

03/30/2021, 2:47 PM

oh right.. i missed your:

Copy code

//isBrowser() && (await fetchApi("/api/users/create", { id, email }))

03/30/2021, 2:48 PM

I think this error is related to your

handlePostSignUp

othiagocruz

03/30/2021, 2:48 PM

even removing this it seems it cached it

03/30/2021, 2:48 PM

Please remove that and see if this error still occurs? That callback is run on the backend only. Not on the frontend.