Skip to content
package.json workflow for native development with Reason/OCaml
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin Executes scripts from the project's root (#881) Mar 18, 2019
design Implement esy workflow in terms of low level primitives (#700) Dec 7, 2018
docs Add documentation for the -C option (#880) Mar 18, 2019
esy-command-expression refmt (#801) Jan 9, 2019
esy-install-npm-release Use node "native" for extracting npm released artifacts (#798) Jan 8, 2019
esy-install Stronger check for installation.json validness (#835) Jan 24, 2019
esy-shell-expansion refmt (#801) Jan 9, 2019
esy-solve 10000000000 is too big for 32bit OCaml ints (#833) Jan 24, 2019
flow-typed/npm test: move jest.config.js at top level Jul 21, 2018
scripts Do not copy esyInstallRelease.js twice Jan 9, 2019
site docs: 0.5.6 Mar 16, 2019
test Windows - Long Paths - Part 2: Check for 'LongPathsEnabled' registry … Feb 8, 2019
.flowconfig Plug'n'play installations (#498) Oct 19, 2018
.gitignore CI: Update build strategies to use latest esy (0.4.3) (#624) Nov 26, 2018
.npmignore Add esy/.npmignore to compensate for esy/.gitignore May 20, 2017
.prettierrc Add .prettierrc Oct 18, 2017
.travis.yml v0.5.7 Feb 24, 2019
LICENSE Create LICENSE Dec 13, 2017
Makefile Update to esy 0.5.0 (#816) Jan 12, 2019 README: mention bin/esy in workflow docs Mar 10, 2019
appveyor.yml Windows: Enable slowtests via appveyor on Windows (#503) Oct 10, 2018
esy.opam Reorganise repo Mar 7, 2018
package.json Bump dev version Feb 24, 2019


package.json workflow for native development with Reason/OCaml.

Build Status

This README serves as a development documentation for esy. For user documentation refer to documentation site.

Repository structure

The following snippet lists esy repository structured (omitting irrelevant or obvious items) with further explanations:

├── Makefile
│   Common tasks and workflows for esy development.
├── bin/esy
│   symlink (wrapper on Windows) for esy command, used for running tests
├── bin/esyInstallRelease.js
│   postinstall step for npm releases produced with `esy npm-release`
│   command. This is a built JS file which is developed in a separate flow
│   inside `esy-install-npm-release/` subdirectory (see below).
├── docs
│   esy end user documentation in markdown format.
├── dune
├── dune-project
├── esy
│   This dune library implements sandbox builder - a routine which builds
│   the enture dependency graph and provides other introspection APIs.
├── esy/bin
│   This dune executable implements "esy" command.
├── esy-solve
│   This dune library implements solver.
├── esy-install
│   This dune library implements installer.
├── esy-build-package
│   This dune library implements package builder. esy library uses this to
│   build each package.
├── esy-build-package/bin
│   This dune executable implements "esy-build-package" command.
├── esy-installer
│   Implementation of installation procedure defined with *.install files.
│   This re-implements opam-installer.
├── esy-install-npm-release
│   Sources for `bin/esyInstallRelease.js`.
├── esy-command-expression
│   Parser for #{...} syntax used in esy manifests.
├── esy-shell-expansion
│   A simple shell expansion.
├── esy-yarn-lockfile
│   Parser for a subset of yarn lockfile format.
├── esy-lib
│   A collection of utility modules shared between other libraries.
├── site
│   Sources for
├── esy.lock
├── package.json
├── scripts
├── test
│   Unit tests.
├── test-e2e-slow
│   End-to-end test suite which takes a significiant amount of time.
│   We execute it on CI by placing `@slowtest` token in commit messages.
└── test-e2e
    End-to-end test suite.


To make changes to esy and test them locally:

% git clone git://
% cd esy
% esy
% esy bootstrap

On Linux/macOS (soon on Windows too) you can run:

% make install-githooks

which will install git hooks which will do pre commit validation.

To test the esy executable in development you can use bin/esy.

Updating bin/esyInstallRelease.js

bin/esyInstallRelease.js is developed separately within the esy-install-npm-release/ directory.


% make bin/esyInstallRelease.js

to update the bin/esyInstallRelease.js file with the latest changed, don't forget to commit it.

Running Tests

Unit tests:

% esy test:unit

E2E tests:

% esy test:e2e


There are two branches:

  • master — the active development, we cut new versions out of there regularly.
  • 0.0.x — maintainance branch for 0.0.x releases.
  • 0.2.x — maintainance branch for 0.2.x releases.
  • 0.3.x — maintainance branch for 0.3.x releases.

Workflow for

To make changes to

  1. Bootstrap site's dev environment:
% make site-bootstrap
  1. Run site locally:
% make site-start
  1. When you are happy with the changes:
% make site-publish


Issues are tracked at esy/esy.

Publishing Releases

esy is released on npm.

Because esy is written in OCaml/Reason and compiled into a native executable we need to acquire a set of prebuilt binaries for each supported platform (Windows, macOS and Linux). We employ CI servers (thanks Azure) to build platform specific releases.

The release workflow is the following:

  1. Ensure you are on master branch and assuming you want to release the version currently defined in package.json (see step 6.), run

    % make release-tag
    % git push && git push --tags
  2. Wait till CI finishes its task and release @esy-nightly/esy package.

    You can test it manually.

  3. Run

    % make release-prepare

    which downloads the nightly corresponding to the current commit working directory is at and "promotes" it to a release. It will create _release/package directory.

  4. Ensure release inside _release/package directory is ok.

    You can cd _release/package && npm pack && npm install -g ./esy-*.tgz to test how release installs and feels.

  5. Run

    % make release-publish

    to upload the release on npm.


    % make NPM_RELEASE_TAG=next release-publish

    To publish release under next tag (so users won't get it automatically but only explicitly requested).

  6. Bump version in package.json to the next patch version.

    We expect next version to be patch version most of the time. In case you want to release new minor or major version you need to bump it before the reelase.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.