`npm i -g reason-cli` install macOS version on linux

[virzen]

Running

npm i -g reason-cli

on Debian outputs

$ npm i -g reason-cli
/home/virzen/.nvm/versions/node/v10.9.0/bin/ocamlmerlin-server -> /home/virzen/.nvm/versions/node/v10.9.0/lib/node_modules/reason-cli/bin/ocamlmerlin-server
/home/virzen/.nvm/versions/node/v10.9.0/bin/ocamlmerlin -> /home/virzen/.nvm/versions/node/v10.9.0/lib/node_modules/reason-cli/bin/ocamlmerlin
/home/virzen/.nvm/versions/node/v10.9.0/bin/ocamlmerlin-reason -> /home/virzen/.nvm/versions/node/v10.9.0/lib/node_modules/reason-cli/bin/ocamlmerlin-reason
/home/virzen/.nvm/versions/node/v10.9.0/bin/refmt -> /home/virzen/.nvm/versions/node/v10.9.0/lib/node_modules/reason-cli/bin/refmt
/home/virzen/.nvm/versions/node/v10.9.0/bin/rtop -> /home/virzen/.nvm/versions/node/v10.9.0/lib/node_modules/reason-cli/bin/rtop
/home/virzen/.nvm/versions/node/v10.9.0/bin/utop -> /home/virzen/.nvm/versions/node/v10.9.0/lib/node_modules/reason-cli/bin/utop
/home/virzen/.nvm/versions/node/v10.9.0/bin/refmttype -> /home/virzen/.nvm/versions/node/v10.9.0/lib/node_modules/reason-cli/bin/refmttype
/home/virzen/.nvm/versions/node/v10.9.0/bin/reactjs_jsx_ppx_v2 -> /home/virzen/.nvm/versions/node/v10.9.0/lib/node_modules/reason-cli/bin/reactjs_jsx_ppx_v2

> [email protected] postinstall /home/virzen/.nvm/versions/node/v10.9.0/lib/node_modules/reason-cli
> node ./esyInstallRelease.js

importing: reason_cli-3.3.3-580ac78e
importing: opam__slash__zed-1.6-1a87600d
importing: opam__slash__yojson-1.4.1-4fc64983
importing: opam__slash__utop-2.2.0-029f4aea
importing: opam__slash__result-1.3-ff74615f
importing: opam__slash__react-1.2.1-d0b77b3e
importing: opam__slash__ocamlfind-1.8.0-f9df3f0a
importing: opam__slash__ocamlbuild-0-8d2a94f9
importing: opam__slash__ocaml_migrate_parsetree-1.0.11-c9719175
importing: opam__slash__merlin_extend-0.3-43ba575e
importing: opam__slash__menhir-20171013-fad93bca
importing: opam__slash__lwt__react-1.1.1-099d2667
importing: opam__slash__lwt__log-1.1.0-0bf17afb
importing: opam__slash__lwt-4.1.0-6b8ce6b9
importing: opam__slash__lambda_term-1.13-27081838
importing: opam__slash__easy_format-1.3.1-4deff5a4
importing: opam__slash__camomile-1.0.1-e92b496f
importing: opam__slash__biniou-1.2.0-35ecab1b
importing: opam__slash__base_unix-base-015d9419
importing: opam__slash__base_threads-base-5a9711e8
importing: opam__slash__base_ocamlbuild-base-bbfb557f
importing: opam__slash__base_bytes-base-06f27e78
importing: ocaml-4.2.3004-aac759d5
importing: esy_ocaml__slash__rtop-3.3.0-26cde351
importing: esy_ocaml__slash__reason-3.3.3-3ee26860
importing: esy_ocaml__slash__merlin-3.0.5005-4f9a1302
tar: Ignoring unknown extended header keyword 'SCHILY.dev'
# ...
tar: Ignoring unknown extended header keyword 'SCHILY.nlink'
Done!
+ [email protected]
updated 1 package in 4.805s

the most important part being

+ [email protected]

This got me figuring out why ocamlmerlin for VSCode doesn't work for two hours or so. Could we do something about it? I might try taking stab at it if you point me in the right direction.

[jordwalke]

The docs state to install the version for your platform. npm install -g reason-cli@latest-macos vs. reason-cli@latest-linux. The reason is that these are large packages and we can't include all things in the package for both platforms (it has to include the compiler infrastructure etc).

[virzen]

Could installing reason-cli itself fail with a message to use platform-specific version then?

[virzen]

Missclick 😅