esy.sh

What It Is

esy is a package management and build workflow tool for native Reason/OCaml projects. Its core idea is to keep project metadata and dependencies in package.json, allowing developers familiar with npm/Yarn to manage the OCaml compiler, Dune, opam packages, and source packages from npm/GitHub in a similar way.

Core Capabilities

Functionally, esy lets you run a single esy command in a project directory to fetch dependencies, install them, and build the project. It creates an isolated sandbox for each project and manages the OCaml compiler and dependencies on a per-project basis, avoiding version conflicts caused by global installations. The documentation highlights parallel builds, a global build cache, clean build environments, filesystem checks, and a lock file, all of which help improve build speed and reproducibility. For opam users, it provides a local development workflow without needing switches; for npm users, it supports using opam packages via the @opam scope and publishing self-contained prebuilt binary packages to npm.

Ecosystem and Documentation

esy integrates closely with Dune, and its examples show the full workflow from hello.ml to dune build, esy b, and esy x. It also supports link: dependencies, which is useful for local multi-project development and testing. The documentation mentions integration with GitHub Actions, VSCode, and @opam/ocaml-lsp-server. Overall, the documentation is solid, covering both “What & Why” and beginner tutorials as well as command references, though it may still have a learning curve for newcomers who are completely unfamiliar with the OCaml compilation model.

Pricing and Support

The main documentation does not mention commercial pricing. Installation is done via npm install -g esy. Community support channels include Discord, Stack Overflow, and GitHub, but there is no visible information about enterprise support, SLAs, or long-term maintenance commitments.

Pros, Cons, and Who It’s For

Its strengths are an approachable npm-style workflow, compatibility with both the opam and npm ecosystems, and solid isolation and caching mechanisms. It is well suited to developers building Reason/OCaml applications, libraries, and command-line tools. Its limitations are that its use case is relatively narrow and mainly focused on the OCaml ecosystem. It also depends on external sources such as npm, GitHub, and opam, so access speed and stability in mainland China are uncertain. If needed, mirrors or proxies may be worth considering, or users can opt for alternatives such as opam and Dune directly.