Skip to content
🚀 Blazing fast, configurable, inferred static type checker for JavaScript.
OCaml Makefile Other
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
Infrared
InfraredCompiler
InfraredParser
InfraredServer
InfraredUtils
assets
meta
test-coverage/Parser
tests
.editorconfig
.gitattributes
.gitignore
.gitmodules
.merlin
.travis.yml
Infrared.opam
InfraredCompiler.opam
InfraredParser.opam
InfraredServer.opam
InfraredUtils.opam
LICENSE
Makefile
README.md
dune-project

README.md

Infrared

Blazing fast, light-weight, inferred static type checker for JavaScript.

Infrared is an configurable & efficient static type checker for JavaScript. This is done by statically inferring a fluid type system onto your entire program – tracking the types of your variables as they change – and raising type errors before they happen at runtime.

What is a Fluid Type System?

A fluid type system is no foreign idea – its a forgiving set of typing rules that change as your program changes. This means no variables are ever committed to a single type – if that variable changes its type somewhere in the program, Infrared keeps track of it.

JavaScript is a dynamic language, and Infrared doesn't want to change that. While other type systems out there want you to change the way you program (and change your JavaScript into something else), Infrared does the opposite.

To understand the way Infrared fits into the typing ecosystem, consider the following:

  • If you're looking for a superset type system that tries to promote soundness, you should use Flow.
  • If you're looking for a superset type system that encourages unsoundness, you should use TypeScript.
  • If you don't want to change anything in your project, but still want to know the types of things in your program + have some type safety at compile time, you should use Infrared.

Planning, Roadmap, and What Lies Ahead

Infrared is a really big project, so naturally it's a pretty good idea to make sure we plan things out carefully to avoid a janky-mess.

I'm using Figma to organize the different sections and responsibilities of each part of Infrared (parser, compiler, server, etc.). Feel free to follow along and check out what I have mapped out so far.

Unfortunately, Figma only reflects the finalized parts of the development roadmap. This means there's a lot of cool work – like typing rules, reduction strategies, discrete proofs, etc – that aren't in this document.

Since those bits are written in a physical notebook, it's hard for me to share publically online. The good news is that I plan on writing a white paper once this project is finished, and all of the cool stuff will be included in there.

Until then, I'm more than happy to chat with anybody who's interested to learn more – feel free to reach out on Twitter.

FAQ

Q – Can I use this?

A – Not yet. This project is still under development, but expect an alpha release soon(ish)!

License

This software is free to use under the MIT License. See this reference for license text and copyright information.

You can’t perform that action at this time.