@i18nprune / core

Runtime-neutral engines for production i18n

This preview is a minimal static page for the @i18nprune/core package on CodeSandbox so the workspace preview has a clear entry point. It is not the full product site; for narrative, diagrams, and install flows, use i18nprune.dev. Point the sandbox static server at this file (or copy it to index.html at the project root if your host expects that path).

Node · CI · programmatic

Construct RuntimeAdapters with createNodeRuntimeAdapters (or web / edge factories), build createCoreContext, then call runValidate, runSync, and friends — same algorithms as the CLI.

What you get

One core, many hosts

Tier A hosts analyze; Tier B hosts read and write locale JSON. The SDK stays data-only — clients handle UX and exit codes.

Validate & scan

Literal keys, dynamic call sites, and structured payloads for CI.

Sync & generate

Deterministic transforms and translator pipelines behind the same contracts.

Install

Add the CLI (ships the SDK)

$ npm i -D i18nprune
$ pnpm add -D i18nprune

In app code, import from @i18nprune/core and the runtime entry that matches your host (@i18nprune/core/runtime/node, /web, or /edge).

Runtimes

Pick adapters for the host

import { createNodeRuntimeAdapters } from '@i18nprune/core/runtime/node';
import { createWebRuntimeAdapters } from '@i18nprune/core/runtime/web';
import { createEdgeRuntimeAdapters } from '@i18nprune/core/runtime/edge';

Surface

Namespaces & ops

The published package exposes focused entry points (/validate, /sync, /generate, …) plus runtime barrels. See the monorepo packages/core/package.json → exports for the authoritative map.

Tip: keep node: imports out of web/worker bundles — only import Node adapters from Node graphs.