Hi, is the types for the default translations from the recipes in supertokens-auth-react exported?

Hi, I have downloaded and installed npx create-supertokens-app@latest which is working ok when i'm using connectionURI: "https://try.supertokens.com" how ever to do some further testing I have also installed supertokens core locally using this guide https://supertokens.com/docs/session/quick-setup/core/without-docker which is also working ok (localhost:3567 is returning 'hello'). However, when i set the connectionURI:"http://localhost:3567" and try to do signup from the front end I'm getting an error "No SuperTokens core available to query"

I am running NextJS with an Express API on a separate server. Is there a way for me to get the user session inside getServerSideProps in my NextJS application? I have tried following the NextJS specific directions for getServerSideProps but it always comes back unauthorized. Any advice? I'm thinking I need to use the SDK inside getServerSideProps which is fine but how do I get the user id or session id so I can check if they have a valid session? My goal is to redirect to a different page if the user is authenticated. My api is running on api.example.com and app on app.example.com on my localhost by adjusting my etc/hosts. I get a session on first page load after logging in, if I refresh the page then it fails with the UNAUTHORIZED error triggering an infinite refreshing loop.

I have a solution that is a mono-repo using Lerna v7 and npm v8. It is using

supertokens-node

.

node_modules

are being hoisted to the root of the repository. Till I was using

v14

of

supertokens-node

, it was being hoisted to the root correctly. There was only one copy of the library. Everything was fine. Since I have upgraded to

v15

though, I have noticed that there is a separate copy of

supertokens-node

in each package where it is being used. Consequently, I am getting the following error on startup.

Error: Please call the supertokens.init function before using SuperTokens

How do I rectify this?

Hi, I’m using Mailjet as a mail platform and would like to send supertokens mails using the service. In the SMTP docs, I can only finds fields for providing a username / password. However, Mailjet only provides me with an API key and secret for the SMTP instead of credentials. Is there a way to configure Mailjet for use with Supertokens anyway?

@rp_st is it possible to delete all users and their data programmatically.

@rp_st There is a problem with the frontend. If I clear the st-last-access-token-update cookie and then try to login/signup, supertokens' backend will start giving error. Even after reloading the page, it won't work. It happened with me earlier also but that was because I was using * in cors , but now that is not the case. My backend supertokens-python version is 0.12.6, in the frontend the versions are: "supertokens-auth-react": "^0.31.1", "supertokens-node": "^13.0.2", "supertokens-web-js": "^0.5.0",

Does supertokens currently support Solid.js/solid-start? If not, is this expected?

Any ideas why my supertokens when deployed doesn't return any cookies but still return 201. But running the same locally I get 201 and cookies? (using postman to test) ?

Hi SuperTokens 🚀, I ran into an issue with CORS when I tried to integrate your ThirdPartyEmailPassword recipe to my application. My Vue.js frontend app is running at "http://localhost:8888" and the NestJS backend api server at "http://localhost:3000". I followed thoroughly your integration guide for NestJS, however after long hours of search, I cannot figure out how to make the CorsMiddleware run before the Supertoken middleware. I get the following CORS error when a request is sent to one of the supertoken core endpoint. Access to fetch at "http://localhost:3000/auth/signup/email/exists?email=johndoe@gmail.com" from origin "http://localhost:8888" has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard ' * ' when the request's credentials mode is 'include'. Here is my main.ts code: async function bootstrap() { const app = await NestFactory.create(AppModule); app.enableCors({ origin: ["http://localhost:8888"], allowedHeaders: ['content-type', ...supertokens.getAllCORSHeaders()], credentials: true, }); app.useGlobalFilters(new SupertokensExceptionFilter()); await app.listen(3000); } bootstrap(); Supertoken config in the **app.module.ts**: @Module({ imports: [ AuthModule.forRoot({ connectionURI: "http://localhost:3567", appInfo: { appName: "IMAT Planner", apiDomain: "http://localhost:3000", websiteDomain: "http://localhost:8888", }, }), ], controllers: [AppController], providers: [AppService, Client], exports: [AppService], }) export class AppModule {} **auth.module.ts**: export class AuthModule implements NestModule { configure(consumer: MiddlewareConsumer) { consumer.apply(AuthMiddleware).forRoutes("*"); } ... } Can you give me an hint on how to make the CORS middleware run before the Supertoken one ?