Explicit Return Type on getUserSession

[Tmmcmasters]

This should fix the typescript issue where some users, including myself, are not seeing the extended properties of the interface UserSession. This should operate as normal.

[Tmmcmasters]

Issue Link: #358

[Tmmcmasters]

This is a very simple PR. I hope that we can get this approved rapidly.

[Tmmcmasters]

I was able to pull this down and utilize this into a broken project. It fixes the type errors that we were receiving

[sandros94]

IMO it should also be added to setUserSession and replaceUserSession, omitting id.

@atinux WDYT?

[Tmmcmasters]

IMO it should also be added to setUserSession and replaceUserSession, omitting id.

@atinux WDYT?

I wil update it if that is what is desired

[Tmmcmasters]

@atinux @sandros94 Just wanted to poke a reminder to please look at this. This has been waiting for approval for two weeks

[atinux]

Sorry for the delay, actually it should be working without having to explicitly set the types, see working example:

Don't you have this in your project?

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/atinux/nuxt-auth-utils@379

commit: a68760b

[atinux]

In that case I believe we should return explicit types for all the exported utils, would you be to do that?

[Tmmcmasters]

In that case I believe we should return explicit types for all the exported utils, would you be to do that?

Let me take a look and see the scope of this. I might be able to do something like this

[Tmmcmasters]

@atinux I updated all server exported functions related to session. Do you want me to update other things?

[Tmmcmasters]

In that case I believe we should return explicit types for all the exported utils, would you be to do that?

Removed the comment to hide some code....

[sandros94]

Sorry for the delay, actually it should be working without having to explicitly set the types, see working example:

[...]

Don't you have this in your project?

I might be wrong but I'm noticing something like a racing condition depending on the ts server version and OS used. And since the local project might be declaring their own User, UserSession this becomes even more evident on some platform like windows

[atinux]

Could you try with:

npm i https://pkg.pr.new/atinux/nuxt-auth-utils@379

And confirm it fixes your issue?

[Tmmcmasters]

Could you try with:

npm i https://pkg.pr.new/atinux/nuxt-auth-utils@379

And confirm it fixes your issue?

Running some testing.

[Tmmcmasters]

@atinux I am receiving an error when trying to install this package;
npm error code UNABLE_TO_GET_ISSUER_CERT_LOCALLY npm error errno UNABLE_TO_GET_ISSUER_CERT_LOCALLY npm error request to https://pkg.pr.new/atinux/nuxt-auth-utils@379 failed, reason: unable to get local issuer certificate npm error A complete log of this run can be found in: /home/tmmcmasters/.npm/_logs/2025-04-03T12_12_02_437Z-debug-0.log

[Tmmcmasters]

@atinux Removed ssl required and ran into a security policy issue so I might not be able to test that. However, whenever I published my fork to a our own npm registry and tested with that, I was able to get it to work and it resolved the Typescript issues that we were facing.

[Tmmcmasters]

@atinux Let me know if the above testing was sufficient