Build configuration

Build configuration controls how Easel turns a source revision into a deployment.

Framework detection

Easel inspects the project files to identify a supported framework and select default commands and output handling. Review the detected framework before the first production release.

Framework detection does not guarantee that every framework capability is supported. See the matching framework guide for the compatibility contract.

Root directory

The root directory identifies the application within the repository. It is especially important for monorepos.

Changing the root directory affects framework detection, dependency installation, build execution, and output discovery.

Install command

The install command restores project dependencies from the committed lockfile.

Prefer deterministic installation:

npm ci

pnpm install --frozen-lockfile

yarn install --immutable

Use a custom command only when the repository requires it.

Build command

The build command creates production output.

Examples:

npm run build

pnpm --filter web build

Framework integrations may provide a default. Override it only when the application needs a custom workspace command or preprocessing step.

Output handling

Static frameworks usually produce an output directory such as dist. Full-stack framework adapters can produce a deployment manifest containing static assets, Functions, routes, and metadata.

Do not configure a static output directory for a full-stack integration unless the framework guide explicitly requires it.

Environment variables

Build-time variables are read while compiling the application. Variables exposed through public framework prefixes can be embedded into browser bundles and must not contain secrets.

Preview and Production builds can use different values.

Runtime configuration

Function runtime, memory, CPU, and other supported settings apply to dynamic output. Use Function configuration for current options.

Configuration precedence

Documented project settings should take precedence over detected defaults. Framework-emitted metadata may apply at route or Function level only when the current Easel build integration consumes it.

Rebuild requirements

Create a new deployment after changing:

• Source code
• Lockfiles or dependencies
• Root, install, or build commands
• Build-time environment variables
• Framework or adapter configuration
• Runtime configuration embedded in build output

Changing traffic assignment between existing Production deployments does not rebuild them.