I think it will be similar to this thread https://discord.com/channels/603466164219281420/603466164219281426/1188498686641176686

https://supertokens.com/docs/passwordless/nestjs/guide#convert-to-a-dynamic-module Add an quote about auth middleware - I think this code example is initially confusing in general, as the middleware is undefined at the moment of reading the tutorial, and later in part 6. the tutorial explicitly states, that AuthModule should implement method and use the middleware https://supertokens.com/docs/passwordless/nestjs/guide#add-service-code I get a TS error for using private config: TS6138: Property  config  is declared but its value is never read. Changing private to protected worked. Might be due to my tsconfig though.

Also I feel that there's an error with how

nest g

is used, as the resulting file structure for me was:

SRC
├───auth
│   ├───auth
│   ├───session
│   └───supertokens
// ...

This resulted in a lot of classes being moved to

/auth/auth

, meanwhile the docs imports them from the same level, for example take the middleware:

ts
import { AuthMiddleware } from './auth.middleware';

whereas after tutorial it looks like this:

ts
import { AuthMiddleware } from "./auth/auth.middleware";

Don't take this of course as some negative criticism. I just wanted to signal, that the docs here aren't 1:1 with the actual code. This problem is of a minor scale, as everything works and nothing is missing in the end

I have one more question - I wanted to setup a dashboard, so I've added a

Dashboard.init()

to the recipe list on the backend (nestjs) side. If I understand correctly, the dashboard should be available under

/auth/dashboard

, so in pair with the API host it will be

localhost:3000/auth/dashboard

for me. However only the html page is being loaded while scripts are not due to CSP

Alright, here's a solution for anyone who's going to read that in the future: if you're using helmet middleware then you have to specify CSP. The simplest way is to disable it for development and enable it for production. reference: https://github.com/graphql/graphql-playground/issues/1283 Whether this is a good or not - make your own judgement

I was just blind. It was just at the bottom of the docs