Build settings

Hiraiship picks each setting from your framework and lockfile. Override any of them when the default doesn't fit.

The settings

Setting	Default	Example override
Install command	From your lockfile: `pnpm install`, `yarn install`, `bun install` or `npm install`	`pnpm install --frozen-lockfile`
Build command	Your framework's, see Frameworks	`npm run build:prod`
Output directory	Your framework's, relative to the project root	`build`
Build machine	Your plan's default	`standard-3`

Each one is independent: overriding the build command keeps the default install command.

For every deployment of a project

In the dashboard, open the project's Settings, then the Build tab. A field left empty uses the default again. The next deployment uses the new settings; deployments already made aren't rebuilt.

The build machine can only be one your plan allows. See Build machines.

For one deployment

The CLI's flags apply to that deployment only, on top of the project's settings:

Terminal

hiraiship deploy \
  --install-command "pnpm install --frozen-lockfile" \
  --build-command "pnpm build:prod" \
  --output-dir build \
  --machine standard-3

Which value wins

For each setting, the first one set:

the deployment's own value (CLI flag);
the project's build settings;
the default for the framework, the lockfile or the plan.

Static sites

A project detected as static is never built: its build command and output directory are ignored.