[QUESTION] req.session.user undefined

[angelhdzmultimedia]

Node: 19.0.0
express-session: 1.17.3
typescript: 4.9.5
express: 4.18.2
@types/express: 4.17.17
@types/express: 1.17.6
tsx: 3.12.3
App Executed with: tsx src/main.ts

I've clicked every result in Google. I don't find the answer!!!

All the examples I see, does the same thing, yet, my req.session.user is undefined in the next requests after I make the request to /auth/login. In my case /auth/user.

I've tried many combinations of saveUninitialized and resave false/true.

Checked if I had the latest version of express-session.

I'm not using nodemon or tsx --watch, so no, the app restarting isn't reseting the cookies/session.

Then I make the post request to /auth/login, I console.log(req.session.user) and bam, all the user's data is there.

Then I make a get request to /auth/user, and req.session.user is undefined.

I tried using req.session.save() on /auth/login and req.session.reload() on /auth/user.
I've tried using req.session.regenerate().

I'm not using cookie: {secure: true} because I don't haven an HTTPS server.

I'm setting a very high maxAge.

Not using cookie-parser middleware as it's not needed anymore.

Tried moving the app.use(session({...})) to different places in the code.

I'm using Rapid API Client extension in VSCode to make the requests.

I'm using app.use('/api/v2', router) as prefix.

But I noticed something:

If I console.log the req parameter, there's a property sessionStore, which has a property sessions, and inside I can see my user's data!!!

[angelhdzmultimedia]

Update

I made a new project, on stackblitz.com, to store, increase, and reset a count number.
It shockingly works great there!!!

https://stackblitz.com/edit/node-ycluk6

The only difference is, in this project, I'm checking if the req.session.count is undefined and I assign a default value.
Oh and Node versions. But I tried on my local project with versions 18.1.0 and 16.18.0 and same issue.

[angelhdzmultimedia]

Update 2

Beliving that I could only store primitives in the session, instead of storing the whole User object, I stored it's id, to later find the user with the id from the users array.

The id from the session comes undefined!!!

[angelhdzmultimedia]

Solved

The counter example worked because I made the requests in the browser, so the session could be stored in cookies.
The other examples, I made the requests via Rapid API Client extension in VSCode (and apparently it doesn't store cookies, new to me). Another test I made, was using another script, that used the node-fetch api, to make the login/register/user requests to the express server, and apparently, that doesn't store cookies as well.

So after I decided to make an user interface in the browser, to test this deeper and to be able to make the request pressing buttons, it worked right away! And then I checked the Application > Cookies and the session was there,
and the user is being returned.

I hope this experience is helpful to someone in the future (or to my forgetful future self wink).

Note: I normally test everything with an user interface in the browser, but this time I'm recording tutorials to teach a relative about NodeJS, TypeScript and soon Vue 3 and Nuxt 3, so that made me go back to the "root", vanilla everything :P

[angelhdzmultimedia]

Update

I managed to get it working in VSCode > Rapid API Client extension.
I just had to pass the Cookie to the /auth/user GET request. Wondering why in the browser it happens automatically...
even though in Rapid API Client extension I have the options:

Anyway, looking great!

[angelhdzmultimedia]

Last Update (I promise!)

The issue was with Rapid API Client VSCode extension.

I switched to Thunder Client extension, and I didn't have to set cookies manually! Phew!!! 😂🙄😔🤡