Releases: Lito-docs/cli
v1.4.1
v1.4.0
What's New
Multi-instance dev server support
Each lito dev session now gets its own isolated project directory (~/.lito/dev-projects/<name>-<hash>/), derived from the input path. You can now run multiple doc servers simultaneously:
lito dev -i ./docs --port 4321
lito dev -i ./other-docs --port 4322Windows EPERM fix
On Windows, stale processes locking .bin/*.exe files are automatically detected and killed before retrying directory cleanup. This fixes the EPERM: operation not permitted, unlink error when restarting the dev server.
Astro template updates
- Replaced
astro-sitemapwith official@astrojs/sitemapintegration - Added
astro-robots-txtfor automaticrobots.txtgeneration - Added
sharpfor image processing
v1.3.3
Fix
- Windows tar extraction: Fixed GNU tar misinterpreting drive letter paths (
C:) as remote hosts on Windows. Paths are now converted to forward slashes and--force-localflag is passed automatically.
v1.3.2
Fixes
- Change default heading font from Syne to Inter for consistency with template defaults
Improvements
- Add
logo.height,logo.alt, andlogo.replacesTitleto core schema validation — templates can now use these options for more flexible logo display
v1.3.1
What's New
Custom Font Support
Users can now configure heading, body, and code fonts via docs-config.json:
{
"branding": {
"fonts": {
"heading": "Syne",
"body": "Inter",
"code": "Fira Code"
}
}
}- Google Fonts URL is built dynamically based on config
- CSS variables (
--font-sans,--font-heading,--font-mono) are overridden at runtime - Defaults to Syne/Inter/Fira Code when not specified
- Works on both doc pages and generated landing pages
v1.3.0
New Features
-
check-linkscommand: Scan documentation for broken internal links withlito check-links -i ./docs. Supports--strictmode for CI pipelines and--quietfor exit-code-only output. -
Content linter: Quality checks for documentation content — catches missing frontmatter, empty files, and common issues.
-
Enhanced
validatecommand: New flags to run all checks in one go:--content— run content quality checks--links— run broken link detection--all— run config + content + links--strict— fail on warnings too (useful for CI)
-
llms.txt integration: Automatically injects
@4hse/astro-llms-txtinto Astro config whenintegrations.llmsTxt.enabledis set indocs-config.json. -
Redirects support: Define redirects in
docs-config.jsonand they're injected into Astro's config automatically.
v1.2.1
Bug Fix
- Fix custom landing pages with full HTML documents: Landing pages that are complete HTML documents (with
<!doctype>,<html>,<head>,<body>) were being nested inside Astro's own HTML wrapper, creating invalid markup. This broke inline scripts (GSAP ScrollTrigger,onclickhandlers), global styles (:rootvariables, animations), and external CDN resources (UnoCSS runtime).
What changed
- Full HTML documents in
_landing/are now parsed and merged correctly into a single valid Astro page <script>and<style>tags in user HTML getis:inlineso Astro passes them through without module bundling or scope isolation- HTML fragments (non-document snippets) continue to work as before, wrapped in Lito's default page shell
v1.2.0
What's New
Custom Landing Page Navbar & Footer
- Support for custom
navbar.htmlandfooter.htmlin the_landing/folder - Automatically replaces the default header/footer on landing pages
- Accepts multiple filenames:
navbar.html,nav.html,header.htmlfor navbar;footer.htmlfor footer - Configurable via
docs-config.jsonlanding settings
Improvements
- Fixed file extension filtering in sync pipeline
v1.1.0
What's New
Added
- Nuxt Framework Support: Full Nuxt template support in the CLI
- Framework detection via
nuxt.config.ts/nuxt.config.jsornuxtdependency - Dev server with
--portflag, build with.output/publicoutput directory - Pagefind search indexing for Nuxt static builds
- Framework detection via
Fixed
- Scaffold Directory: Moved dev-project directory from
/tmp/.litoto~/.lito/dev-projectto fix bundler resolution issues (e.g. Turbopack failing to resolvenode_modulesfrom/tmp)
Full Changelog: v1.0.0...v1.1.0
v1.0.0 — Stable Release
Lito v1.0.0 — Stable Release
The first production-ready release of Lito, the open-source Mintlify alternative for generating documentation sites from Markdown.
Highlights
- Production-Ready: Out of beta — stable, tested, and ready for real-world use
- Dual Publishing: Available on both npm (
@litodocs/cli) and GitHub Packages (@lito-docs/cli) - Tiny Package: 39 KB on npm (down from 31 MB)
What's New in 1.0.0
Added
- GitHub Packages publishing alongside npm
- Privacy policy and terms of service pages for sample docs
- MIT License for the Astro template
Changed
- Decluttered navbar — version/language switchers moved to sidebar, social links reorganized
- Header now contains only: search, GitHub, theme toggle, and CTA
- Version and language switchers work in both sidebar and mobile navigation
- CLI version reads dynamically from
package.json— no more version drift
Fixed
- CLI version mismatch across
package.json, commander, and update checker - npm package reduced from 31 MB (743 files) to 39 KB (31 files)
- Removed invalid
mainentry pointing to non-existent file - Sidebar scroll position persistence after layout refactor
Install
npm install -g @litodocs/cliQuick Start
lito init -o ./my-docs -n "My Docs"
lito dev -i ./my-docsFull Changelog: https://github.com/Lito-docs/cli/blob/main/CHANGELOG.md