Can someone hwlp me out with difference between we...
# support-questions-legacyp
paras
03/16/2023, 10:33 AMCan someone hwlp me out with difference between web-js and auth-node package, I was using web-js as mentioned for own ui, and was trying to add custom login provider to support for linkdln, but getting error for defining
signInAndUpFeature Copy code
Argument of type '{ signInAndUpFeature: { providers: { id: string; name: string; buttonComponent: JSX.Element; }[]; }; }' is not assignable to parameter of type 'UserInput'.
Object literal may only specify known properties, and 'signInAndUpFeature' does not exist in type 'UserInput'.ts(2345)r
rp_st
03/16/2023, 10:34 AMhey @paras which version of the sdks are you using?
n
nkshah2
03/16/2023, 10:40 AMHi @paras if you are using the web-js SDK then there is no additional setup required with SuperTokens for your custom provider on the frontend
In the docs you want to generally refer to the "Plain Javascript" tab if its present for web-js docs. Some pages will also have a way to switch between auth-react and web-js docs in the top right of the content
p
paras
03/16/2023, 4:29 PMlatest only,
n
nkshah2
03/17/2023, 5:18 AMYou're referring to the auth-react SDK docs @paras . Refer to this message
p
paras
03/19/2023, 6:12 AMI didn't find the way to switch bw, an I got confused b/w auth-react anfd web-js
as far as I can Understand, with own ui uses web-js and pre-built uses auth-react for frontend
paras
03/19/2023, 6:14 AMFor my case I was using my own ui that means - web-js for frontend, and I was trying to setup custom login via Linkedln and was getting issues
export function getApiDomain() {
const apiPort = process.env.REACT_APP_API_PORT || 3001;
const apiUrl = process.env.REACT_APP_API_URL || `http://localhost:${apiPort}`;
return apiUrl;
}
export function getWebsiteDomain() {
const websitePort = process.env.REACT_APP_WEBSITE_PORT || 3000;
const websiteUrl = process.env.REACT_APP_WEBSITE_URL || `http://localhost:${websitePort}`;
return websiteUrl;
}
export const SupertokenConfig = {
appInfo: {
appName: "Demo App",
apiDomain: getApiDomain(),
websiteDomain: getWebsiteDomain(),
},
// recipeList contains all the modules that you want to
// use from SuperTokens. See the full list here: https://supertokens.com/docs/guides
recipeList: [
ThirdPartyEmailPassword.init({
signInAndUpFeature: {
providers: [
{
id: "linkedin",
name: "Linkedin",
buttonComponent: <div style={{
cursor: "pointer",
border: "1",
paddingTop: "5px",
paddingBottom: "5px",
borderRadius: "5px",
borderStyle: "solid"
}}>Login with Linkedin
}
],
}}
),
Session.init(),
],
};
export const recipeDetails = {
docsLink: "https://supertokens.com/docs/thirdpartyemailpassword/introduction",
};
n
nkshah2
03/20/2023, 7:22 AMRight so where did you get the
signInAndUpFeaturep
paras
03/20/2023, 10:06 AMn
nkshah2
03/20/2023, 10:15 AMRight so the frontend has a tab for plain javascript for that. But yeah the custom providers need no additional setup on the frontend for web-js. You just need to do the backend setup
p
paras
03/21/2023, 3:52 AMI did the same, and still getting issues
n
nkshah2
03/21/2023, 3:54 AMYou should see error logs for that in your backend
p
paras
03/21/2023, 4:09 AMBackend is running in docker and could't find any logs related to this
n
nkshah2
03/21/2023, 4:11 AMWhat backend framework are you using?
p
paras
03/21/2023, 4:12 AMNodeJs
n
nkshah2
03/21/2023, 4:12 AMExpress?
p
paras
03/21/2023, 4:12 AMyes
n
nkshah2
03/21/2023, 4:13 AMIn your backends default error handler you can log the error out and you should see logs for them in the docker logs
p
paras
03/21/2023, 4:13 AMokk, lemme try this too
paras
03/21/2023, 4:51 AMI used the error handler like this https://supertokens.com/docs/passwordless/custom-ui/init/backend, still no logs
n
nkshah2
03/21/2023, 5:30 AMI mean the default error handler for your express app (the express docs can explain how to set it up), not the SuperTokens error handler
p
paras
03/21/2023, 8:16 AMthe
/auth/signiniprevoked by userr
rp_st
03/21/2023, 8:17 AMare you calling the api yourself in a useEffect in react?
p
paras
03/21/2023, 8:18 AMno.
r
rp_st
03/21/2023, 8:18 AMthen? Can you give me more context?
p
paras
03/21/2023, 8:22 AMI was running the core in my local i.e docker
and when I click signup with linkedln, the authurl is not fetched properly everytime,
but when it gets fetched, I see two calls for /signinup in my network tab
one gets failed with status code 500
and one gets successful
sometimes both gets failed with axios error, when checked I found it was an issue with bearer token
r
rp_st
03/21/2023, 8:26 AMyou are using our pre built UI? And that is making 2 calls to the signinup API? Is that correct?
p
paras
03/21/2023, 8:30 AMnope, I used my own UI and getting 2 calls
paras
03/21/2023, 8:31 AMbut no where in my code I made call to /signinup
r
rp_st
03/21/2023, 8:32 AMare you calling the signinup function from web-js somewhere? There has to be some place where a call is being made to this API, else how can it be made (since it's your own UI)
p
paras
03/21/2023, 8:37 AMI have no mention of /auth/signinup in my code
paras
03/21/2023, 8:37 AMso probable from core only it's getting called twice
r
rp_st
03/21/2023, 8:37 AMCore doesn’t call this api
rp_st
03/21/2023, 8:37 AMSearch for signinup in your code
p
paras
03/21/2023, 8:42 AMso from where does it get called?
r
rp_st
03/21/2023, 8:42 AMyou must be calling it in your code. Please check
rp_st
03/21/2023, 8:42 AMit's an API that's called from the frontend to the backend
p
paras
03/21/2023, 8:49 AMn
nkshah2
03/21/2023, 8:50 AMSearch without the "/"
p
paras
03/21/2023, 8:50 AMstill no instance
n
nkshah2
03/21/2023, 8:52 AMAh sorry search for
signinandupp
paras
03/21/2023, 8:54 AMr
rp_st
03/21/2023, 9:15 AMyea so this is the issue. In dev mode in react, react calls useEffects twice
rp_st
03/21/2023, 9:15 AMso you need to solve for that - ask in the react community please or google it
p
paras
03/21/2023, 9:46 AMokkh thanks
7 Views