Hm, I don't know of this, will check it out!

Yea. See the code snippet I sent above. It uses that with

ssr: false

option.

Which does what you want..

Oh, that dynamic.. Ok cool

but anyway, what you did makes sense too.. so if it works, that's great :))

Yeah, but I wanted to keep SSR in some way

The only problem is this: > Warning: Did not expect server HTML to contain a in . Because of the mismatch

But it's no showstopper, I might send a PR if I figure it out

cool!

Btw, is there any problem with using ThirdPartyEmailPassword but only for email?

no problem

but i'd still recommend you use just EmailPassword since the configs provided to you are more focused on email password login. Plus things like API overrides are focused on that too. Finally, the bundle size on the frontend will be slightly smaller if you use that

Okay cool, thank you!

I implemented your first suggestion here and it worked great! I also managed to add extra fields, with a username that checked with the backend if it was available. Really smooth, thank you! Now I'm thinking if I could prefill an extra field. I want to have an "invite code" field so people don't have to wait for approval, and I want to send this in an email. I was thinking I could create a link like

/auth?code=foobar

and it would autofill.

Yea. You could do that. You could add JS to the page which will take that value and add it to the right input field.

Can I somehow modify the state of

SuperTokens.getRoutingComponent

for this?

You would need to embed the sign in up component in /auth and then you can add any JS to that. See https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/embed-sign-in-up-form

Okay, cool, I almost thought so!

Or, you can use the component override feature to do this as well.

See this: https://supertokens.io/docs/thirdpartyemailpassword/advanced-customizations/react-component-override/usage

Unrelated btw, but if you do

<http://example.com>

the link preview never show in Discord

ooooo! that's nice.

thanks

np!

In my backend config I put this

js
{
  id: 'inviteCode',
  validate: async (inviteCode: string) => {
    const isCodeValid = await inviteCodeCheck.backend(inviteCode);
    console.log('isCodeValid', isCodeValid);
    if (!isCodeValid) {
      console.log('Invalid invite code, Invalid invite code');
      return 'Invalid invite code';
    }
  },
},

under

js
ecipeList: [
  ThirdPartyEmailPasswordNode.init({
    signUpFeature: {
      formFields: [

but it's never triggered, nothing is logged. How would I debug this?

Have you put something similar on the frontend as well? With the same id?

Also, the form fields r only for if someone does login via email and password login.

Yes

login? But it's under signUpForm

Ah yea. I meant sign up with email & password