Deploy a Nuxt app that uses Bun

Q: How do I change the Bun install command?

Run ezhst build set --install " ", then ezhst redeploy. Pass an empty string to return to auto-detection.

EasyHost picks Bun when it finds bun.lock or bun.lockb. There is nothing to configure, and these are the exact commands it runs for Nuxt.

Last updated November 9, 2026

What EasyHost runs

Step	Command
Lockfile	`bun.lock or bun.lockb`
Install	`npm install -g bun && bun install --frozen-lockfile`
Build	`nuxt build`, through your package build script
Start	`scripts.start`, or `node .output/server/index.mjs` when no start script exists

Scripts run with bun run <script>. Dev dependencies are available during the build, and the app runs with NODE_ENV=production.

Deploy

Nothing to change. EasyHost detects Nuxt, and the Node server output reads PORT and HOST.

npx ezhst projects create my-project --link
npx ezhst apps create my-app
npx ezhst link --project <project-slug> --app <app-slug>
npx ezhst env import .env
npx ezhst deploy

Things to watch with Bun

Bun installs and runs your scripts, but the base image is Node. Runtime APIs that only exist in Bun need a custom start command, such as bun run src/index.ts.

Commit bun.lock or bun.lockb. Without any lockfile, EasyHost falls back to npm install. To replace the install step, run ezhst build set --install "<command>".

Next steps

See the Nuxt hub for every Nuxt guide, or free Nuxt hosting for what is included.

Frequently asked questions

How do I change the Bun install command?

Run ezhst build set --install "<command>", then ezhst redeploy. Pass an empty string to return to auto-detection.

Start for free

Install the skill, choose Global or Local, then tell your agent to deploy. No credit card, no config files.

npx ezhst skill install