This guide installs the public Eden CLI and prepares the local tools used by Eden Deploy.
Eden currently supports:
- macOS or Linux
- Node
>=24.17.0 - a Cloudflare account
Native Windows and Bun as the JavaScript runtime are not supported. Bun may install the package, but Eden itself always runs on Node.
Check Node before installing:
node --versionThe result must be v24.17.0 or newer. Eden intentionally has no artificial
upper Node major-version bound.
Install only @moinulmoin/eden. npm resolves the Cloudflare runtime companion
package automatically.
Choose one installer.
npm install --global @moinulmoin/eden@0.4.1pnpm add --global @moinulmoin/eden@0.4.1bun add --global @moinulmoin/eden@0.4.1Bun is an installer only. Do not run Eden with bunx --bun.
Confirm the installed command:
eden --helpThe help output must list preflight, deploy, and destroy.
Deploying to Cloudflare uses Wrangler 4.120.0. The account must be on the
Workers Paid plan, which Cloudflare Containers requires. Authenticate the
Cloudflare account that owns the target Workers:
npx wrangler@4.120.0 loginConfirm the selected account:
npx wrangler@4.120.0 whoamiReview the returned account before deploying. Eden never selects a different Cloudflare account silently.
On macOS, a stale registry.cloudflare.com keychain entry makes the managed
registry login fail with The specified item already exists in the keychain (-25299); remove it with
security delete-internet-password -s registry.cloudflare.com and retry.
Deploying an existing Eve project also requires Docker or OrbStack with Linux/amd64 container support.
Check the container engine:
docker versionThe Eve project must contain all of the following at its selected root:
- an exact
packageManager: "pnpm@..."value inpackage.json - the matching root
pnpm-lock.yaml - a project-local Eve executable resolved through
node_modules/.bin/eve - the providers, databases, Workflow World, credentials, and external services that the Eve application already requires
Eden does not add or replace those project-owned services.
Continue with Deploy an existing Eve project.
Use the same installer that owns the global command.
npm install --global @moinulmoin/eden@latestpnpm add --global @moinulmoin/eden@latestbun add --global @moinulmoin/eden@latestThen confirm the command still starts:
eden --helpnpm uninstall --global @moinulmoin/edenpnpm remove --global @moinulmoin/edenbun remove --global @moinulmoin/edenUninstalling the CLI does not delete Cloudflare resources. Remove an Eve
deployment with eden destroy first.
Eden does not install package managers or modify shell configuration. If the
selected installer is missing or its global commands are not on PATH, follow
that tool's official installation guide:
After configuring the installer, open a new shell and run eden --help. Do not
install duplicate Eden copies with multiple package managers to hide a PATH
problem; ownership of updates and uninstallation becomes ambiguous.
- Deploy an existing Eve project
- All documentation: Documentation index