Astro i18n — DevOps skill for Claude Code

@edgekits/astro-i18n

Edge-native i18n for Astro on Cloudflare Workers. Translations live as data in Workers KV, one JSON value per locale and namespace, so the server renders every page in its language and nothing ships to the client; changing a string is a KV write, not a redeploy. Each namespace is cached at the edge under its own URL, and `edgekits-i18n migrate` purges only the namespaces whose content changed through the Cloudflare Purge API. The default locale's JSON files define a typed schema: the CLI generates the `I18n.Schema` declaration, so `t.common.hero.title` is checked by TypeScript and a missing key is a compile error.

The design is explained in the edgekits.dev series: [Stop Shipping Translations to the Client, Part 1](https://edgekits.dev/en/blog/edge-native-i18n-astro-cloudflare-part-1/), [Part 2](https://edgekits.dev/en/blog/edge-native-i18n-astro-cloudflare-part-2/) and [Stop Redeploying to Update Translations (Part 3)](https://edgekits.dev/en/blog/granular-edge-cache-purge-astro-cloudflare-part-3/).

Requirements

• Astro ^7.3 with output: 'server' and the @astrojs/cloudflare adapter ^14.3.
• wrangler ^4.125, installed in the project (a peer dependency: the CLI runs the project's own wrangler for its KV writes).
• A wrangler.jsonc (the CLI reads that file; wrangler.toml and wrangler.json are not read).
• Node >=22.
• A Workers KV namespace bound as TRANSLATIONS.
• For migrate only: the site on a proxied Cloudflare zone, its zone ID, and an API token with the Zone › Cache Purge permission.

Quick start

1. Install

npm i @edgekits/astro-i18n

2. Bind a KV namespace

npx wrangler kv namespace create TRANSLATIONS

Add the namespace to `wrangler.jsonc` under the binding name `TRANSLATIONS`:

{
  "compatibility_date": "2026-09-01",
  "kv_namespaces": [{ "binding": "TRANSLATIONS", "id": "" }],
}

3. Write `edgekits-i18n.config.ts`

At the project