| Crates.io | ezno-checker |
| lib.rs | ezno-checker |
| version | 0.0.18 |
| created_at | 2023-02-25 18:10:33.167872+00 |
| updated_at | 2024-11-13 19:52:47.489167+00 |
| description | A fast and correct TypeScript type checker with additional experiments |
| homepage | https://kaleidawave.github.io/posts/introducing-ezno |
| repository | https://github.com/kaleidawave/ezno |
| max_upload_size | |
| id | 794480 |
| size | 1,190,656 |
Contains type checking logic for TypeScript and logic for running type checking checks over ezno-parser.
See specification for all currently implemented checking features.
At the moment it comes packaged with internal.ts.d.bin. This can either be a syntactic or binary definition of methods, types and such in the runtime.
While the checker is indented for the Ezno toolchain and its parser, most (3/4) of the checker code is AST agnostic. The synthesis directory that contains the bindings with ezno-parser can disabled with no-default-features. You can build your own AST <-> Type checking APIs using it for adding Ezno's type checking features into other toolchains (without needing to parse or convert ASTs).
#TODO ASTImplementation, synthesis folder rule
A sparse documentation of some to the internals of the functions, structures and processes exists in the /documentation folder.
Set EZNO_DEBUG to any value to trace diagnostic information from the crate::utils::notify! macro (In powershell = $Env:EZNO_DEBUG=1)