-
-
Notifications
You must be signed in to change notification settings - Fork 68
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 inference for options and arguments works in rc.5 but fails in rc.7 #764
Comments
Weird, seems the problem is very flaky. Adding Maybe an issue with JSR/VS Code/TS/Deno/Deno lint/something else? |
@lionel-rowe adding the Using:
|
FWIW I just ran into this. Not sure what's unique about my system, apart from running WSL & VsCode.
Interestingly when I tried the same directly on Windows, no issues.
|
And similarly now it's come good in WSL & all I did was:
ie: nothing too special. I can only assume it's somehow related to deno's cache. |
I have the same error, it works with rc 4 and stops with rc 5 (fedora 41 ) Screencast.From.2024-12-10.22-43-18.mp4 |
Cannot get it to work in rc.7 whatsoever, rc.5 works out-of-the-box. |
I remember having this problem from time to time in the past. But currently I can't reproduce it. I tested it again with all rc versions, on two different laptops, with deno and node+typescript. I also think it's either an lsp or a caching issue. Does anyone have this issue with node as well? |
It fixed itself when I explicitly run |
In rc.5,
options
is correctly inferred as{ verbose?: true | undefined }
andargs
asstring[]
; however, in rc.7, bothoptions
andargs
implicitly haveany
type unless manually annotated.The text was updated successfully, but these errors were encountered: