-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Type error compiling with typescript #3837
Closed
rcocks-hl opened this issue
Jun 27, 2023
· 3 comments
· Fixed by #3860, #3879, DTS-STN/passport-status#667, LetsSmash/namethesongs#10 or FelixAshong/signin-sigu-ppage#8
Closed
Type error compiling with typescript #3837
rcocks-hl opened this issue
Jun 27, 2023
· 3 comments
· Fixed by #3860, #3879, DTS-STN/passport-status#667, LetsSmash/namethesongs#10 or FelixAshong/signin-sigu-ppage#8
Labels
Comments
Yeah, |
This worked for me: |
Hi, what's the status of this please? The suggested workaround of |
Merged
This was referenced Aug 21, 2024
This was referenced Sep 20, 2024
This was referenced Sep 22, 2024
[Snyk] Upgrade: , react, react-dom, , , , formik, next, use-remote-data
alvinrumbaoa/photography#133
Open
This was referenced Sep 22, 2024
This was referenced Oct 28, 2024
This was referenced Nov 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Current Behavior
Typescript compilation fails with type errors in Formik library
The npm package
hoist-non-react-statics
hasn't been updated in years, so seems unlikely to be an upstream issue.Typescript version 4.9.5.
Expected behavior
Compilation should suceed without type errors.
Reproducible example
I don't have an easily shared reproduction, but this is my package-lock info:
react-hoist-non-statics is satisifed with 3.3.2, as it has been for a while:
Suggested solution(s)
Not sure if this requires manual typing or setting a typescript version dependency.
Additional context
This happened after upgrading from Formik 2.4.1 to 2.4.2.
Your environment
The text was updated successfully, but these errors were encountered: