We have some more questions about the old helper functions moving from

supertokens-web-js

to

supertokens-website

. I will make a thread!

In

supertokens-website

we had to manually call the APIs. For the third party login, I used the function:

export const getThirdPartyAuthUrl = async ({
  thirdPartyId,
}: {
  thirdPartyId: 'google' | 'facebook' | 'apple'
}): Promise<GetThirdPartyAuthUrlResponse> =>
  fetch(
    `${url}/api/auth/authorisationurl?thirdPartyId=${thirdPartyId}`,
    {
      method: 'GET',
      headers: {
        'Content-Type': 'application/json',
        rid: 'thirdpartyemailpassword',
      },
    },
  ).then(res => res.json())

And then onThirdPartyLogin I would call:

export const onThirdPartyLogin = async ({
  provider,
  platform,
  repository,
}: {
  repository: Repository
  provider: 'google' | 'facebook' | 'apple'
  platform: Platform
}) => {
  const response = await getThirdPartyAuthUrl({
    thirdPartyId: provider,
    repository,
  })

  if (response.status === 'OK') {
    const url = new URL(response.url)
    if (platform === 'APP') {
      console.log('app came here')
      url.searchParams.append(
        'redirect_uri',
        `${
          repository === 'CONTRACTOR'
            ? REDIRECT_URL_CONTRACTOR
            : REDIRECT_URL_CLIENT
        }/api/auth/redirect?provider=${provider}`,
      )


      window.open(url)
    }
    if (platform !== 'APP') {
      url.searchParams.append(
        'redirect_uri',
        `${
          repository === 'CONTRACTOR'
            ? FRONTEND_URL_CONTRACTOR
            : FRONTEND_URL_CLIENT
        }/auth/callback/${provider}`,
      )
      window.location.href = url.href
    }
  }

  if (response.status !== 'OK') {
    alert(`Er is iets misgegaan met inloggen via ${provider}, probeer opnieuw`)
  }
}

Because I am using Capacitor as well, I had to have different redirect URI's, I couldn't just redirect to the callback, had to go to API first. Should I overwrite in

supertokens-web-js

or something? And what functions should I use?

Thank you for your time and we look forward to your answer 🌈

For the

CookieHandlerInterface

and

WindowHandlerInterface

, the

supertokens-web-js

SDK inherits types from

supertokens-website

so you can keep that as it is.

supertokens-website

is a dependency of

supertokens-web-js

so the import will still be available after migrating

What about the helper functions?

So you should never need to call the APIs manually anymore