QwikCity adapter not configured for the deploy target in CI

QwikCity needs a platform adapter to produce a deployable server build. Run qwik add for your host (static, express, cloudflare-pages, vercel-edge) so qwik build emits the right entry and output; without it, the deploy fails or ships a client-only bundle.

What this error means

The client build succeeds but there is no server output, or the deploy fails to find a function entry, because no matching adapter was added and qwik build.server did nothing useful.

Error: Missing QwikCity adapter output.
No entry.cloudflare-pages.tsx found. Run:
  npm run qwik add cloudflare-pages

Common causes

No adapter added for the target

Without an adapter, QwikCity has no server entry or build integration for the platform, so the server output is missing or wrong.

The wrong adapter for the host

Using the static adapter for a host that expects serverless functions (or vice versa) produces an artifact the platform cannot run.

How to fix it

Add the adapter for your platform

1. Run qwik add <adapter> for the host (static, express, cloudflare-pages, vercel-edge).
2. Commit the generated adapter entry and updated build scripts.
3. Use the adapter build script in CI.

npm run qwik add cloudflare-pages
# or: express, static, vercel-edge, netlify-edge

Verify the server output exists

Assert the adapter output directory is present so a missing adapter fails the build, not the deploy.

- run: npm run build
- run: test -d dist || (echo "no adapter output" && exit 1)

How to prevent it

• Add the QwikCity adapter matching your deploy target.
• Commit the adapter entry and build scripts.
• Assert the expected build output in CI.

Related guides