• r

    rp

    11 months ago
    no worries! happy to help 🙂
  • M̸̹̣i̼̗č̹̰o̧̲ͅ

    M̸̹̣i̼̗č̹̰o̧̲ͅ

    11 months ago
    its a good lib btw, i am very grateful it exists ❤️
  • r

    rp

    11 months ago
    thank you! 😃) Happy to hear this
  • KitsuneKenshi

    KitsuneKenshi

    10 months ago
    Hey, I have run into an issue with
    req.session
    , where it seems like TS does not detect
    session
    as a property of Request. I did tried to fix it somehow or find answer of what may be causing it, but couldn't find anything helpful. Here I only found one question related to this issue and the answer wasn't really helpful. I'm using Nuxt 2 with Vue and express. If I could get any help with that it would be great.
  • r

    rp

    10 months ago
    Hey @KitsuneKenshi you can import SessionRequest type from supertokens-node/framework/express and make the req object of that type.
  • r

    rp

    10 months ago
    That would work cause SessionRequest extends Express.Request and adds the session object type to it.
  • KitsuneKenshi

    KitsuneKenshi

    10 months ago
    thanks I'll try it in a second
  • constantinos

    constantinos

    10 months ago
    Hello, How can we make multi-domain front-ends work with SuperTokens? In our SPA app, we allow our users to add their own custom domains via CNAME records e.g. planner.domainA.com and planner.domainB.com. This way they can use our app as a white label on their sites for their customers to use. Auth is something we do not offer right now, but we want to add an Auth solution in which they would visit planner.domainA.com/login to login etc. What is the easiest solution to achieve this? Basically, we are looking for a solution similar to Shopify where each user can setup their own shop and auth for each shop. Do we need a multitenancy approach? Supertokens do not support this I can see. Is there a way to make this work with one front-end domain e.g. auth.ourPrimaryDomain.com/domainA for logging in the user and then redirecting them to the custom domain e.g. planner.domainA.com? While keeping the session in the front-end.
  • r

    rp

    10 months ago
    So all the domains talk to the same backend api domain? Or do they have different API domains?
  • constantinos

    constantinos

    10 months ago
    Currently its 1 backend api. We just change the logo based on the domain. We want to change it so that each domain has their own orders and catalogues.