Repository files navigation

Reason toolchain packaged for npm.

Supported: Installing viaNPM/Yarn, on Mac OS or Linux.

Fornpm users, usenpm install -g reason-cli@latest-macos or@latest-linux instead.

The package's size is rather big. It takes a while to download,especially on slower internet. If npm is stuck and doesn't produce anyerrors then it's probably just downloading it. This will be fixed in thefollowing releases. Sorry.

The installation requires glibc >=3.4.21. If you're on macOS, you should be good to go. If you're on Ubuntu, reason-cli requires Ubuntu16.04. Otherwise the postinstall might fail.

If you are having trouble, you can download the tarball to your machine separately, and runnpm install path/to/tarball, to install from the local file.

Pick your favorite editor pluginhere

Just reinstall over the previously installed package. It's usually a good ideato uninstall the old reason-cli first.

npm uninstall -g reason-clinpm install -g reason-cli@latest-macos

When installed withnpm install -g,reason-cli places the following toolsin your path:

• ocamlmerlin
• ocamlmerlin-reason
• refmt
• rtop

Repeat the following for both most recent reason-cli linux and macos circle CIbuilds that succeed.

0. Bump the versions/config inpackage.json to your liking, and make sure tolocally runesy install to regenerate any lockfiles. Send a commit withthose lockfiles and config changes.
1. When that diff builds onmaster, grab the results from theArtifactstab on the CircleCI build results for the build of the platform you want torelease.
2. Verify the release can be installed:npm remove -g reason-cli && npm install reason-cli.tar.gz
3. Make surertop works.
4. Uninstall the release you just installed:npm remove -g reason-cli(otherwise npm freaks out).
5. Extract the release locally:tar -xvf reason-cli.tar.gz.
6. cd package
7. Edit the version number inpackage.json to be3.3.2-linux or3.3.2-macos (adjust for the version and platform you downloaded foraccordingly).
8. npm publish

Repeat steps 1-8 for both linux and macos builds.

9. Update dist tags:

   npm dist-tags add reason-cli@3.3.2-linux latest-linuxnpm dist-tags add reason-cli@3.3.2-macos latest-macos

   (adjust for the version and platform you downloaded for accordingly)

You can just recreate what the circle CI steps do locally and then perform the steps above.

• For failed installs try:

  npm install -g whateverReasonCliReleaseYouTried --ignore-scriptscd whereverYourGlobalNpmPackagesAreStored/reason-cli/./postinstall.sh

  • Does it give any better information about what is failing?
  • Is there a specific log file that it claims the actual error is written into?

• Did you remember to install using-g?

• When updating, did you try to uninstall the previous installation?

Each published binary includes the built-in ability to troubleshoot where eachbinary is resolved to. If something is going wrong with yourrefmt command,you can see which released binaryrefmtactually invokes in the release. Weuse the----where flag with four- characters because it's unlikely toconflict with any meaningful parameters of binaries likerefmt.

refmt ----where> /path/to/npm-packages/lib/reason-cli/actualInstall/builds/reason/bin/refmt

SeeORIGINS.