actions-marketplace-validations/esy - Github Action

Run cached esy install and esy build

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stale
License: None

Inputs

name	description	required	default
cache-key	A cache key for esy.json/esy.lock.	yes	—
source-cache-key	A cache key for retrieving esy sources cache.	yes	—
working-directory	Working directory for esy. It's converted into an absolute path, if it already isn't	no	—
esy-prefix	Prefix of esy folder	no	—
manifest	JSON or opam file to be used	no	—
ocaml-compiler-version	Version of ocaml compiler (in semver. Eg. 5.1.0 or 4.10.1000) Optional, but mandatory if prepare-npm-artifacts-mode and bundle-npm-artifacts-mode is used. This is because, these version strings affect the relocatability logic while both preparation mode, and while postinstall scripts are generated during bundling mode.	no	—
prepare-npm-artifacts-mode	Runs a steps that prepare artifacts for release the app to NPM. These artifacts are later used by, `bundle-npm-tarball-mode`.	no	—
bundle-npm-artifacts-mode	Runs a steps that bundle artifacts for release the app to NPM.	no	—
postinstall-js	Path to a custom `postinstall.js` file that could be placed in the final bundled NPM tarball.	no	—
setup-esy	Flag to control if esy itself should be installed by the action	no	—
setup-esy-tarball	URL to esy tarball. Must be provided together with shasum and version. Else, the action will default to latest from NPM	no	—
setup-esy-shasum	shasum of the tarball. Must be provided together with shasum and version. Else, the action will default to latest from NPM	no	—
setup-esy-version	version of the esy tool. Must be provided together with shasum and version. Else, the action will default to latest from NPM	no	—
setup-esy-npm-package	Alternative NPM package that contains esy. Can contain version/tag too. Eg esy@beta.	no	—

Outputs

no outputs