@mdwrk/extension-language-pack-studio
v1.0.8
Published
First-party language-pack authoring extension for MdWrk hosts that need localization inspection, catalog editing, and language-pack workflow surfaces inside the extension system.
Readme
@mdwrk/extension-language-pack-studio
First-party language-pack authoring extension for MdWrk hosts that need localization inspection, catalog editing, and language-pack workflow surfaces inside the extension system.
This package provides the bundled manifest, runtime entrypoint, workspace module, command registration, action-rail item, settings section, and sample-pack assets for MdWrk language-pack authoring.
Why
Use it when localization authoring should remain an extension concern instead of being hard-wired into the app shell. The package owns the studio extension boundary; the host still supplies catalog storage, workspace state, and persistence.
What
- Bundled extension metadata for the language-pack studio surface.
- A
createLanguagePackStudioBundledEntryfactory for registering the studio command, workspace module, action-rail placement, and settings. - Catalog loading helpers and sample packs for host integration and tests.
Installation
Node.js 20.x through 22.x, matching the workspace engine contract in the root package manifest.
npm install @mdwrk/extension-language-pack-studio @mdwrk/extension-runtimeUsage
Load it from a host that already provides the MdWrk extension runtime, i18n services, and workspace state.
import { createLanguagePackStudioBundledEntry } from "@mdwrk/extension-language-pack-studio";
const languagePackStudioEntry = createLanguagePackStudioBundledEntry({
controller: host.languagePackStudioController,
});The package also exposes ./manifest, ./types, ./version, and ./bundled subpath exports for hosts that load extension metadata separately from bundled entry registration.
Related
- Packages index - family and package navigation
- Root README - repo overview
