create-openmerge

Production-ready OpenMerge project initializer. It supports greenfield applications and additive adoption by existing projects.

npm init openmerge@latest my-app
npm create openmerge@latest my-app
pnpm create openmerge@latest my-app
npx create-openmerge@latest my-app

On Windows PowerShell, the npm.ps1 shim consumes the literal -- option separator. The zero-option command above works as written; when passing initializer options, invoke npm.cmd so npm receives and forwards the separator:

npm.cmd init openmerge@latest -- customer-app --template nextjs --package-manager npm --yes --no-install

Templates

• nextjs — customer-facing widget, server-only credential boundary, link-token route, linked accounts, incremental sync, unified reads, and writeback.
• express — authenticated-backend-ready REST routes over @openmerge/core.
• node — headless operational client for account inventory, sync dispatch, and unified reads.

Existing projects are detected by the presence of package.json. Their manifest is semantically merged and existing OpenMerge files are never replaced unless --force is explicit.

Deterministic / CI usage

pnpm create openmerge@latest customer-app \
  --template nextjs \
  --package-manager pnpm \
  --workspace-id ws_example \
  --api-url https://api.openmerge.example \
  --embed-url https://connect.openmerge.example \
  --yes --no-install

Use --dry-run to inspect the exact file plan. The CLI intentionally has no API-key flag: command-line secrets leak into shell history, process inspection, and CI logs. Generated local environment files are gitignored and contain a blank key.

Run create-openmerge --help for all options.