-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Missing Console
methods
#118
Comments
Yep there are many definitions missing. You can see the latest and there the ezno/checker/definitions/full.d.ts Lines 146 to 149 in 4143369
In TypeScript's definition file you can find these methods here: Ezno requires more information (or at least benefits from, it still works but isn't as accurate) about internal methods than is present in the TypeScript definition But the best way to solve is to create a script that creates a hybrid file, that rewrites some more detailed Ezno definitions into the large definition files found in the TypeScript repository. This would automate mismatches like this with Aside: I assume as you are just testing it out as at the moment the checker is unstable and not ready for real world projects. But for the future, if you find you are blocked by missing methods/properties on internal types, you can use interface merging. interface Console {
debug(...items: any[]);
}
console.debug(23) // should now work |
I recommend adding builtin types as soon as possible. Even if it's not complete, it would help catching edge cases, and maybe help with design decisions or implementation details. |
console.debug('hello world')
is reported byezno check
as invalid, however nearly all runtimes (most browsers, Bun, Deno, Node.js) support different logging level methods (debug
,info
,warn
,error
).https://developer.mozilla.org/en-US/docs/Web/API/console
The text was updated successfully, but these errors were encountered: