Official Next.js starter 1.0.0
1 October 2026 — first stable release of qiick-io/externa-next-starter (v1.0.0), paired with Externa Core 1.1.0. GitHub Release · Headless starter.
Who this is for
Teams building a Next.js App Router site against the Public CMS API who want a minimal, server-only fetch client — not a marketing theme.
What shipped
- Node 24 pinned in
.nvmrcfor local/CI consistency. - Collection-agnostic setup — no hard-coded
postsdefault; auto-discover readable collections; setup panel + OpenAPI ping when none yet. - Modular client under
lib/externa/(types,client,collections,openapi) with English JSDoc. - README documents
develop(integration) vsmain(releases).
How to start
git clone https://github.com/qiick-io/externa-next-starter.git
cd externa-next-starter
# use the 1.0.0 tag for this cut; prefer latest patch later
git checkout v1.0.0
cp .env.example .env.local
EXTERNA_API_URL=http://externa-core.test
EXTERNA_API_KEY=
EXTERNA_COLLECTION=
nvm use # Node 24
npm install
npm run dev # http://localhost:3002
Leave EXTERNA_COLLECTION empty to auto-pick the first readable collection. Grant Read on that collection for the public role (or your API key’s role). Docs: Public CMS API.
Compatibility: use with externa-core ≥ 1.0.0; OpenAPI ping expects core ≥ 1.1.0 for GET /api/v1/openapi.json.
Later patches
Security bumps for Next/React landed as 1.0.1 and 1.0.2 — see Starters security patches (Oct 2026). For a full blog walkthrough on this starter, see Build a blog with Next.js and Externa.
Sources
Related
- PHP emergency security releases — Oct 2026
PHP CVEs 2026-109618 and 2026-109619 (CVSS 9.2 RCE). Update to 8.4.27 or 8.5.12; what Externa users must do.
- Externa Core 1.2.1 — field rename drafts & deps
Patch for draft/revision field renames, npm audit clean-up, and the repair-renamed-field-drafts artisan command.
- Nuxt starter 1.1.1 — NuxtPage and Node 22.13+
Why 1.1.1 matters: NuxtPage instead of slot, h3 pin for getQuery, engines ≥22.13.0 — plus what 1.1.0 tooling bumps included.