A JavaScript compiler and TypeScript checker written in Rust with a focus on static analysis and runtime performance.
You can try what it current supports today with npx
npx ezno check file.ts
Or download the binary with npm install ezno
, cargo install ezno
or on GitHub releases. Or try it in Oxc!
What Ezno is
- A type checker for JavaScript, usable as a library or with optional compiler infrastructure (parser, CLI, LSP, etc)
- Fully typed programs, guaranteeing type safety (as long as definitions are sound)
- Types aimed at soundness and tracing for better static analysis
- A imperative type system, with event tracing and evaluating function side effects. Equivalent to an interpreter, but with types rather than values
- A collection of experiments of types. Some features work well, others are in the prototype stage. Some are specific to JavaScript, others could be applied to other dynamic languages
- A challenge to the status quo of DCE, type checking and compilation through deeper static analysis beyond syntax analysis
- Written in Rust
What Ezno is not
- eNZo, Z goes before the N (pronounce as 'Fresno' without the 'fr') 😀
- 1:1 / parity with TSC, it has different behaviors but should work in existing projects using TSC (check out stc that is aimed at 1:1)
- A binary executable generator. It takes in JavaScript (or TS/Ezno superset) and does similar methods to traditional compilers, but at the end emits JavaScript. However the event intermediate representation could be used in the future to generate a lower level format
- Usable, still a way to go until it can check actual programs. See the specification for what is currently implemented in the checker
Read some more detailed posts
This project is a workspace consisting of a few crates:
Also checkout oxc_type_synthesis, a crate which allows using the type checker through oxc!
Check out issues and comment on discussions! Read CONTRIBUTING.md for more information.