Hey there. I resumed my work today implementing the session recipe and I'm basing it on this: https://app.swaggerhub.com/apis/supertokens/FDI/1.13.1 What is rid supposed to be here? the recipe id?

meaning of rid

Small feedback regarding supertokens docs UX: In example codeblocks, if you select a part of the code and copy paste, the selected code is pasted in a single line with broken formatting, however clicking the "Copy" button in the codeblock works as expected and the code is pasted with correct formatting

hmm. thanks! that is strange. Can you open an issue about this in our docs repo?

Will do, thanks!

thank you!

Just checked the repo now, a similar issue already exists: https://github.com/supertokens/docs/issues/303

👍

Hey, was curious to know the reason for running with a

Web Component

for the default SuperTokens auth UIs instead of running with regular HTML/JS. Was it to make the UI more easily transferrable between frontend frameworks (assuming they supported Web Components)?

We don't use web components on its own. We use react components (which uses web components)

As in React uses web components? Or as in the React component uses Web Components?

React component uses Web Components

Ah, okay. So then I'm assuming web components weren't used to make it easy for transferring between frontend frameworks. Was there a different advantage instead?

yea! react is awesome, and very very popular

most people geenrally use react, angular or vue. And we wanted to natively support the most popular of the three. So we chose react

and you can render the react components in angular / vue as well.

Ah interesting. Are there plans to support other frameworks in the future? Been trying to think of a way to make an easily transferrable UI.

Not at the moment. We do provide a vanilla JS SDK which can be used in any framework on top of a custom UI. The SDK providers all the helper functions you would need

Okay cool. Good to know. Is there a place in the codebase where the Web Component is located for reference?

Not sure what you mean. The whole supertokens-auth-react SDK is full of react components

Yes. But isn't there a section that has the logic for writing out the Web Component portion that's used? Or is all of that also defined within a React Component? I've never used Web Components before so I don't know what the code for making one looks like. 😅

https://github.com/supertokens/supertokens-node/pull/348 Wasn't sure how to go about creating a new branch? Is that my responsibility or someone else's? It seems like I don't have permissions to create a new branch in the

supertokens-node

repo.

You don’t need to create a new branch. Creating a PR to master is fine

Awesome

We just forked

supertokens-node

to add Cloudflare Worker support (in a React/Remix context). Anybody else working on that ?

Hey @Contrebande ! That’s cool! Lmk how we can help - if you have any specific questions around how things are setup.

Also, if you scroll up on this thread, you will find there is a repo that has remix + supertokens support

Thanks ! I will check it out! I will let you know of specific questions.

Just checking to see if there's still interest in this: https://github.com/supertokens/supertokens-node/pull/348. I think I addressed all the comments.