Build configuration

Build configuration controls how Easel turns a source revision into a deployment. Set it in Project settings → Build. Changes apply to the next deployment.

Framework detection

Easel inspects your project files to detect a supported framework and pick default commands and output handling. Check the detected framework before your first production release. Detection doesn't mean every framework feature is supported. See your framework guide for what is.

Root directory

The root directory is where your application lives in the repository, and builds run from there. Changing it changes framework detection, dependency installation, and where Easel looks for build output. For repositories with several applications, see Monorepos.

Install command

The install command restores dependencies from your committed lockfile. Prefer a deterministic install:

npm ci

pnpm install --frozen-lockfile

yarn install --immutable

Build command

The build command produces your application's output. Framework integrations provide a default, so override it only when you need a workspace command or a preprocessing step:

pnpm --filter web build

The build command must exit when the build is done. Don't start a long-running server from it: Easel runs your functions for you.

Output

Static frameworks usually produce an output directory such as dist. Full-stack frameworks produce static assets, functions, and routes together. Don't set a static output directory for a full-stack framework unless its framework guide says to.

Function memory, CPU, duration, and Node.js version are set separately. See Function configuration.

Environment variables

Builds read the variables for the deployment's environment, and variables with a public prefix are embedded in browser code. Changes apply to new deployments. See Environment variables.

When to rebuild

A deployment keeps the source and settings it was built with. Create a new deployment after you change source code, dependencies, lockfiles, the root directory, install or build commands, build-time variables, or framework configuration. Promoting or rolling back moves traffic between deployments that are already built and doesn't rebuild them.

Build machines

Builds run on the machine selected in Project settings → Build. Enhanced uses included build minutes twice as fast. See Build pricing.

For build duration, bundle size, and upload limits, see Limits. On Hobby, builds stop once the month's included build minutes are used.