@solcreek/nitro

Nitro preset for Creek. Deploy any Nitro-powered app to Cloudflare Workers (managed Creek) or self-hosted creekd with a one-line config change.

Because Nuxt, SolidStart, TanStack Start, and Analog all build on Nitro, this single preset covers all four frameworks.

Install

# Nitro v3 (bare Nitro apps, future Nuxt 5, etc.)
npm install -D @solcreek/nitro nitro

# nitropack v2 (current Nuxt 4, SolidStart 1.x via Vinxi, TanStack Start,
# Analog, and anything else that hasn't migrated to v3 yet)
npm install -D @solcreek/nitro nitropack

Either nitro@>=3.0.260522-beta or nitropack@>=2.13.0 satisfies the peer dependency. Same preset code drives both — nitropack (v2) and nitro (v3) are the same project at different majors, and the preset surface we use is stable across the bump.

Framework support today

Framework	Bundled engine	Status with @solcreek/nitro
Nuxt 4	nitropack@^2.13	✅ verified (Nuxt 4.4.6 E2E)
SolidStart 1.x	nitropack@^2.x (via Vinxi)	✅ verified (SolidStart 1.3.2 E2E)
TanStack Start	nitro@^3.0 (via nitro/vite)	✅ verified (TanStack Start 1.168.11 E2E — Nitro v3)
Bare Nitro v3	nitro@^3.0	✅ verified (conformance + 56 official scenarios)
Analog	nitropack@^2.x	🟡 blocked — Analog 2.5.2 vite-plugin-nitro still on h3@1 which conflicts with Nitro v3's h3@2 in mixed workspaces. Pure Analog projects untested.
SolidStart 2	(no Nitro — uses srvx + h3 directly)	❌ out of scope after they dropped Nitro

Two targets, one package

Target	Subpath	Underlying preset	When to pick it
Cloudflare Workers (managed Creek edge)	@solcreek/nitro/workers	cloudflare-module	You want one-command global edge deploys via creek deploy.
creekd (self-host, Linux supervisor)	@solcreek/nitro/creekd	node-server	You want to run the app yourself on a VPS with cgroup isolation.

Swap targets by changing one string — same source, different nitro.config.ts.

Workers usage

// nitro.config.ts
export default defineNitroConfig({
  preset: "@solcreek/nitro/workers",
  compatibilityDate: "2026-05-23",
  cloudflare: {
    wrangler: {
      compatibility_flags: ["nodejs_compat"],
    },
  },
});

Then:

nitro build      # produces .output/server/{index.mjs, wrangler.json}
creek deploy     # ships it

For Nuxt: put the same block under nitro: { ... } in nuxt.config.ts. Same for SolidStart, TanStack Start, and Analog (their config keys differ; the Nitro options inside are identical).

Resource bindings

D1, R2, KV, Queues, AI, Durable Objects, cron triggers — everything goes through the standard Nitro cloudflare.wrangler namespace. Creek's deploy pipeline reads the generated wrangler.json directly; nothing adapter-specific to learn.

creekd usage

// nitro.config.ts
export default defineNitroConfig({
  preset: "@solcreek/nitro/creekd",
  compatibilityDate: "2026-05-23",
});

Build, then point creekctl at the manifest:

nitro build
creekctl up myapp --from .output/.creek-creekd/manifest.json

The build emits a .creek-creekd/manifest.json validated against the @solcreek/creekd-manifest schema. creekd reads it to know which runtime to spawn (node / bun / deno), which port to bind, and which health-probe path to hit.

Overrides

export default defineNitroConfig({
  preset: "@solcreek/nitro/creekd",
  // Custom namespace, read by @solcreek/nitro at build time.
  // @ts-expect-error not in NitroConfig — it's our own.
  creek: {
    port: 8080,                  // default: 3000
    runtime: "bun",              // default: "node"
    healthCheckPath: "/healthz", // default: "/_creek/health"
  },
});

Design notes

Why creekd needs a manifest but Workers does not

• creekd runs outside Cloudflare. creekctl needs a process contract telling it which runtime to spawn, what port, what health probe. That contract is .creek-creekd/manifest.json.
• Workers deploys via Wrangler / CF API. The entire configuration is already in wrangler.json — adding a sibling manifest would create a no-op consumer and a sync-drift hazard.

So @solcreek/nitro/workers is a deliberately thin wrapper around cloudflare-module with no compiled hook. The thinness is the feature.

Why one package and not two

Both presets share the same intended audience ("I have a Nitro app and want it on Creek") and ~80% of the supporting code (env handling, manifest shaping, fixture infrastructure). Splitting into @solcreek/nitro-workers + @solcreek/nitro-creekd would force users to pick a target before installing, and version-skew the shared layer.

Conformance

The package ships with a vendored copy of Nitro's official preset conformance harness (test/conformance/, sourced from nitrojs/nitro at v3.0.260522-beta). Smoke tests in test/smoke/ run the full nitro build against minimal fixtures for both targets to validate the build contracts.

License

Apache-2.0