-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Ability to skip type checking of remote modules #5460
Comments
I suggest something like:
(The "default" is chosen when the option isn't given. If it is given, it requires a value.) |
@kitsonk what's your take on this issue? |
It seems like a lot of work which would cause a level of confusion. I think we should land the binary capability to skip type checking and live with that for a while before making the whole thing more complicated. |
So |
|
The TS compiler has a
--skipLibCheck
compiler option that allows skipping type checking of declaration files.Similarly, it might be nice for Deno to:
Have a way to not type check the private implementations of remote modules or make this the default (this would help with compile times too).
Have something like the
--skipLibCheck
compiler option that skips type checking of remote modules completely or have a way to do this on a case-by case basis. Example, in deps.ts people could add a comment above the import:The reason why this would be nice is because remote modules are often out of our control and we might want to depend on an old version of a dependency that now has type checking errors in the current version of the TS compiler being used.
The text was updated successfully, but these errors were encountered: