-
Notifications
You must be signed in to change notification settings - Fork 475
1.x.x to 2.x.x migration type issue #540
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The latest build of |
@cjbarth In fact, the same issue happens without @types/passport-saml package. I have reinstalled modules with the version 2.0.5 and got the same error. |
I confirm what @vbodnia says, please reopen this issue, it's a current bug in v2.0.5. |
Is this a bug at the |
@cjbarth Yes it is: |
It seems this might be related to #549. Would you agree? In any case, I can't see from your screen shot exactly what the problem is. Do you have some sample code I can load up? |
The screen shot doesn't show it, but the original description is very similar to mine. I haven't gone back with tweezers yet to figure out where mine went wrong. |
|
v3 of |
Env: Node 14.15.4
Typescript 4.1.3
Currently, I am using [email protected] with @types/[email protected]. After updating to 2.0.5 I've got a type error in MultiSamlStrategy saying:
The problem is that I'm also extending express requests with custom fields, e.g. user.
The text was updated successfully, but these errors were encountered: