Esbuild is an installer and runner for esbuild.

Profiles

You can define multiple esbuild profiles. By default, there is a profile called :default which you can configure its args, current directory and environment:

config :esbuild,
  version: "0.23.0",
  default: [
    args: ~w(js/app.js --bundle --target=es2016 --outdir=../priv/static/assets),
    cd: Path.expand("../assets", __DIR__),
    env: %{"NODE_PATH" => Path.expand("../deps", __DIR__)}
  ]

Esbuild configuration

There are four global configurations for the esbuild application:

• :version - the expected esbuild version

• :version_check - whether to perform the version check or not. Useful when you manage the esbuild executable with an external tool (eg. npm)

• :cacerts_path - the directory to find certificates for https connections

• :path - the path to find the esbuild executable at. By default, it is automatically downloaded and placed inside the _build directory of your current app

Overriding the :path is not recommended, as we will automatically download and manage esbuild for you. But in case you can't download it (for example, the npm registry is behind a proxy), you may want to set the :path to a configurable system location.

For instance, you can install esbuild globally with npm:

$ npm install -g esbuild

On Unix, the executable will be at:

NPM_ROOT/esbuild/node_modules/@esbuild/TARGET/bin/esbuild

On Windows, it will be at:

NPM_ROOT/esbuild/node_modules/@esbuild/win32-x(32|64)/esbuild.exe

Where NPM_ROOT is the result of npm root -g and TARGET is your system target architecture.

Once you find the location of the executable, you can store it in a MIX_ESBUILD_PATH environment variable, which you can then read in your configuration file:

config :esbuild, path: System.get_env("MIX_ESBUILD_PATH")