What's the recommended way to make the

NextApiRequest

and express'

Request

types match? I see that in the nextjs example basically works with supertoken's express adapter and imports the

import { middleware } from 'supertokens-node/framework/express';

which TypeScript doesn't like. https://github.com/supertokens/next.js/blob/canary/examples/with-supertokens/pages/api/auth/%5B%5B...path%5D%5D.js

hey!

sure! I prefer type casting it as of now

hmm. that is interesting

e.g. your example for

with-localstorage

also has some types off https://github.com/supertokens/supertokens-auth-react/blob/master/examples/with-localstorage/api-server.js @rp_st should we pass input.res to the updateHeaders rather than

session

?

yea.. it's input.res. Not session.res

Okay, should I submit a PR for this?

Yes. Please do. thanks!

So it will never be undefined, unless you set it to undefined instead of giving a function

So you can handle it by throwing an error in the if block - cause it will never come thrrr

There's also a return missing for the signOutPOST method (expects

{status: "OK"}

) If I get the implementation working, I can add it to the above PR by fixing the example. 😅

Right! Thank you!

Okay, I have to throw in the towel. I was unable to make supertokens work for my use case 😦

What is your use case?

Making the

with-localstorage

example work on nextjs

An right. That is a complex customisation., why do you need to use localstorage?

Ahh I see