-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
use local typescript if installed. #85
Comments
Agree, maybe one can use something like |
I don't think it's that easy, unfortunately, I think |
Yes, seems like it hence #62, would be good if that patching could eventually be removed and upstreamed to core, but probably easier said than done |
@voxpelli By the way, I have been using expect-type instead of tsd for a while now, has worked perfectly for me, maybe it works for your use case too. |
Just released a new version with TypeScript@4.1 support. I'm working on an automated solution which creates a patched TypeScript release whenever TypeScript itself creates a new release. Together with allow testing multiple TypeScript versions, it should automatically be picked up on the next test run. I'm going to close this for now because as you said, I need a patched TS which doesn't work if I use the locally installed TypeScript version. |
typescript@4 support variadic tuple type & labeled tuple about 2 month ago.
The vscode can understand the code, but tsd can not.
The text was updated successfully, but these errors were encountered: