#checker #static-analysis #javascript-compiler #checking #ezno #binary #typescript

macro binary-serialize-derive

A small representation for objects in the Ezno checker, used for caching to make checking faster

2 releases

0.0.1 Jun 7, 2023
0.0.0 Jun 7, 2023

#49 in #static-analysis

Download history 191/week @ 2023-12-17 236/week @ 2023-12-24 163/week @ 2023-12-31 224/week @ 2024-01-07 75/week @ 2024-01-14 14/week @ 2024-01-21 19/week @ 2024-01-28 11/week @ 2024-02-04 24/week @ 2024-02-11 50/week @ 2024-02-18 57/week @ 2024-02-25 47/week @ 2024-03-03 41/week @ 2024-03-10 31/week @ 2024-03-17 33/week @ 2024-03-24 55/week @ 2024-03-31

166 downloads per month
Used in 2 crates (via ezno-checker)

MIT license

84 lines

A JavaScript compiler and TypeScript checker written in Rust with a focus on static analysis and runtime performance.

[!IMPORTANT] Ezno is in active development and currently does not support enough features to check existing projects. Check out the getting started guide for experimenting with what it currently supports.

What Ezno is

  • A type checker for JavaScript usable through a CLI (with a LSP also in the works)
  • A high level library that allows type checking to be added to other tools!
  • Checks programs with guaranteed type safety (no runtime TypeErrors) (as long as definitions are sound)
  • Types aimed at soundness and tracing for better static analysis
  • A imperative type system that tracks and evaluates the side effects of functions and control flow structures. It is similar to an interpreter, but acts with types instead of values and does not run IO side effects etc
  • A collection of experiments of types. Many are being worked out and are in the prototype stage. Some of the new behaviors benefit JavaScript specifically and others could be applied to other languages
  • Written in Rust
  • Fast and Small
  • Open source! You can help build Ezno!
  • A challenge to the status quo of type checking, optimisations and compilation through deeper static analysis beyond syntax analysis

What Ezno is not

  • eNZo, the Z is in front of the N (pronounce as 'Fresno' without the 'fr') 😀
  • Be on parity with TSC or 1:1, it has some different behaviors but should work in existing projects using TSC
  • Faster as a means to serve large codebases. Cut out bloat and complex code first!
  • Smarter as a means to allow more dynamic patterns. Keep things simple!
  • A binary executable compiler. It takes in JavaScript (or a TypeScript or Ezno superset) and does similar processes to traditional compilers, but at the end emits JavaScript. However in the future it could generate a lower level format using its event (side-effect) representation

Read more about Ezno

This project is a workspace consisting of a few crates:

Crate Lines Of Code Contains
checker checker lines of code Stores for types and contexts, type checking logic and optional synthesis over the parser AST
parser parser lines of code AST definitions, logic for parsing, AST to string and visiting

Help contribute

Check out good first issues and comment on discussions! Feel free to ask questions on parts of the code of the checking implementation.

Read CONTRIBUTING.md for information about building and testing.


~35K SLoC