Deployment

Cloudflare Pages

Curvea projects can be deployed to Cloudflare Pages directly from source. The normal workflow does not commit dist.

Repository setup

Commit the project source, package.json, and lockfile. Generated Curvea projects already ignore:

node_modules
dist

The project should declare @curvea/cli as a local dev dependency.

Use:

Build command: npm run build
Build output directory: dist
Node.js: >=20.19.0

The dependency-install step should install the project's lockfile dependencies. In a clean CI environment, the equivalent local workflow is:

npm ci
npm run build

npm run build invokes the locally installed curvea build command from the project script.

For a normal Cloudflare Pages project domain or custom domain, use:

{
  "site": {
    "basePath": "/"
  }
}

Only configure a non-root base path when the deployed site is actually served below a subpath.

Set site.url to the final public origin before validating canonical URLs or enabling sitemap generation.

After deployment, verify routes, CSS, JavaScript, public assets, favicon, canonical URLs, and sitemap.xml when enabled.

The release checklist performs that live Cloudflare validation separately; this page documents the intended build configuration only.

1 min read