my-project
, produces single sharable library named
my-project
and a single executable named MyProject
.npm install -g esy@next
git clone git@github.com:jordwalke/esy-peasy-starter.git
esy install
esy build
name
field in the package.json
and rebuild..re
file in bin/
becomes the MyProject
executable.lib/
becomes the my-project
named library..re
file can automatically see the my-project
library as the
YourProjectLib
module.my-project
library, which then allows them to see the YourProjectLib
module.Use the standard esy x any-command-here
command to run any-command-here
as
if you had installed the package. For example esy x YourPackage --args
builds
and runs your YourPackage
executable with arguments.
lib/
directory if everything fits into the single file in bin/
.bin/Index.re
file to be
bin/YourProjectNameCamelCased.re
.esy add @opam/dep-name@version
automatically builds and adds a new
dependency to package.json
.esy ls-libs
.package.json
like this: "peasyLibs": ["the-library-name"]
.esy build
.Note: After adding/building a new dependency you can use
esy ls-modules
to see which named modules become available to you by adding thepeasyLibs
entry.
npm
.Use esy
to make prebuilt binary releases of your program that can be installed
from plain npm
.
esy release bin
cd _release/bin-darwin
npm publish --tag darwin
esy-peasy
is good for rapidly making new small executables/libraries. Once they
grow, you'll want to "eject out" of esy-peasy
and begin customizing using a more
advanced build system.