Okay. I've been working on this for awhile. It still is not finished, and it can probably be improved upon. But here's my running example of using

Remix

with `SuperTokens`: https://github.com/ITenthusiasm/remix-supertokens Does SuperTokens ever review this kind of stuff? If it's written correctly, it should enable people to get auth up and running without end users needing to enable JavaScript. It might also give new ideas for the default forms exported by SuperTokens. If it's written incorrectly or I'm missing any use cases / error cases (specifically within login/signup/resetting passwords), I can try to fix those. 🙂 The 2 things I hope to add in the future are specified in the TODO list. (They are JS-enhanced forms and a local db example... if I find time.)

oh! real cool!

I could be doing it wrong entirely! That's why I want someone to review it. 😂

haha well.. have you tried to get session refreshing to work? That definitely requires JS

Don't think so. I just wanted to get the basics down with logins/logouts/resets. If

supertokens-website

handles the session refreshing for us, then it shouldn't be too hard to add that into the app.

yup!

The app isn't "progressively enhanced" yet. I still need to add the ability for error states to disappear after interaction and a couple other things. Trying to figure out the cleanest way to bring in JS and still have it work for people without JS.

See this: https://github.com/supertokens/supertokens-auth-react/blob/master/examples/with-jwt-localstorage/api-server/index.ts#L89

Sweet. I'll check this out when I get the chance.

Hey @ITEnthusiasm will have a look sometime this week

Sounds good! I added a tiny bit of client-side validation while waiting.

hey @ITEnthusiasm i opened 2 issues in the repo. Also, could you explain how the APIs exposed by the SuperTokens middleware are being called?

Thank you! I responded to the build problem GH Issue. I'll try to look at the second one soon (hopefully later today).

cool!

Yeah so the SuperTokens auth routes are handled by Remix's backend. The

action

functions in Remix routes are responsible for handling form submissions. So if you look at the

action

function inside the

login.tsx

route, you'll see that I'm grabbing the login data and then sending it to the SuperTokens route in a way that it can understand. Since the SuperTokens routes exist on the same server, this results in the server making a request to itself. This is necessary in order to guarantee that I can leverage how Remix handles forms (and to guarantee that people can login without JS). However, from what I understand, when Remix sees that the server is making a request to itself, it will instead invoke the appropriate middleware without making any HTTP requests (thankfully).

understood! this makes sense. I'll have a look at this app once again

Thanks!