Fix SuperTokens to use separate ThirdParty and EmailPassword recipes
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -1,7 +1,5 @@
|
||||
import ThirdPartyEmailPassword, {
|
||||
Google,
|
||||
Github,
|
||||
} from "supertokens-auth-react/recipe/thirdpartyemailpassword";
|
||||
import ThirdParty, { Google, Github } from "supertokens-auth-react/recipe/thirdparty";
|
||||
import EmailPassword from "supertokens-auth-react/recipe/emailpassword";
|
||||
import Session from "supertokens-auth-react/recipe/session";
|
||||
|
||||
export const frontendConfig = () => {
|
||||
@@ -16,7 +14,7 @@ export const frontendConfig = () => {
|
||||
websiteBasePath: "/auth",
|
||||
},
|
||||
recipeList: [
|
||||
ThirdPartyEmailPassword.init({
|
||||
ThirdParty.init({
|
||||
signInAndUpFeature: {
|
||||
providers: [
|
||||
Google.init(),
|
||||
@@ -24,6 +22,7 @@ export const frontendConfig = () => {
|
||||
],
|
||||
},
|
||||
}),
|
||||
EmailPassword.init(),
|
||||
Session.init(),
|
||||
],
|
||||
};
|
||||
|
||||
Reference in New Issue
Block a user