If you use either of them, you can use our supertokens-website SDK

On line 35 & line 38, there are calls to our supertokens service. This supertokens-service being used is a simple service wrapping like two functions from the Supertokens SDK. Here's a gist of it; https://gist.github.com/martinAlt335/3424b56d0bb04761f463a0940a60d264 Line 12 you will see

apiDomain

make sure to change that to wherever your supertokens API is, we have that set in our Angular environment file. You will also see cookieService being used in the super-tokens service. It's this npm package; https://www.npmjs.com/package/ngx-cookie-service; make sure to add it to your module.

@rp Now that I think about it, in the second gist I shared, on line 24, we are manually deleting the

sIRTFrontend

cookie, when implementing we found that without deleting this, a user would not be signed out properly. Is there a function within Supertokens that handles this without us having to do it manually? I do recall when implementing, when calling the browser sdk sign out function, ‘sIRTFrontend’ cookie would be left as residue. Everything else seemed to work, manually removing this cookie looks like it does the trick. Is there anything should be done differently?