v0.19.1 (preview)
A safer default installer and lossless adoption for existing libraries.
npm create storylarkis the supported publisher path — it installs and locks compatible engine, Worker, and pipeline packages; records project provenance; and includesnpm run doctorchecks for local and live configuration. Cloning the engine remains the advanced path for contributors and forks, and a clone is not installed untilnpm installcompletes- Existing Cloudflare resources can be adopted safely without renaming them or changing the deployment's brand identity
- Repo adoption is matching-only and atomic — StoryLark compares the complete chapter set, rendered content, order, visible metadata, and cover identity before changing ownership. Narration, timings, voices, and content objects are preserved; a mismatch writes nothing
- No-op syncs are truly no-op — unchanged content keeps its narration and metadata, and a second identical sync reports zero writes
- Repository reads now start at the configured path and batch authenticated Markdown requests, keeping large private repositories within the Cloudflare Workers Free subrequest budget
- Standalone stories and multi-chapter books are both first-class inputs, including legacy single-story chapter ids and root-relative artwork
Found a gap? StoryLark is open source — improve these notes on GitHub.