Skip to content

Releases: Lito-docs/cli

v1.4.2

15 Mar 14:43

Choose a tag to compare

Windows Compatibility Fixes

  • Fix bsdtar extraction failure: Removed --force-local flag that is not supported by Windows' built-in bsdtar. Uses forward-slash paths instead to avoid drive letter (C:) issues.
  • Fix process.env.HOME on Windows: Replaced with os.homedir() in info and doctor commands — HOME is undefined on Windows, causing invalid cache paths.
  • Fix python3 not found on Windows: Preview server fallback now uses python on Windows, where python3 is not typically available.

Install / Upgrade

npm install -g @litodocs/cli@1.4.2

v1.4.1

02 Mar 16:47

Choose a tag to compare

Fixes

  • Windows llms.txt generation: Wrapped @4hse/astro-llms-txt plugin to fix dir.pathname returning /C:/Users/... on Windows, which caused doubled drive letters (C:\C:\...) and file-not-found errors during build.

v1.4.0

02 Mar 16:23

Choose a tag to compare

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 4322

Windows 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-sitemap with official @astrojs/sitemap integration
  • Added astro-robots-txt for automatic robots.txt generation
  • Added sharp for image processing

v1.3.3

02 Mar 16:05

Choose a tag to compare

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-local flag is passed automatically.

v1.3.2

25 Feb 00:12

Choose a tag to compare

Fixes

  • Change default heading font from Syne to Inter for consistency with template defaults

Improvements

  • Add logo.height, logo.alt, and logo.replacesTitle to core schema validation — templates can now use these options for more flexible logo display

v1.3.1

19 Feb 16:56

Choose a tag to compare

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

19 Feb 13:57

Choose a tag to compare

New Features

  • check-links command: Scan documentation for broken internal links with lito check-links -i ./docs. Supports --strict mode for CI pipelines and --quiet for exit-code-only output.

  • Content linter: Quality checks for documentation content — catches missing frontmatter, empty files, and common issues.

  • Enhanced validate command: 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-txt into Astro config when integrations.llmsTxt.enabled is set in docs-config.json.

  • Redirects support: Define redirects in docs-config.json and they're injected into Astro's config automatically.

v1.2.1

16 Feb 16:00

Choose a tag to compare

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, onclick handlers), global styles (:root variables, 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 get is:inline so 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

12 Feb 15:51

Choose a tag to compare

What's New

Custom Landing Page Navbar & Footer

  • Support for custom navbar.html and footer.html in the _landing/ folder
  • Automatically replaces the default header/footer on landing pages
  • Accepts multiple filenames: navbar.html, nav.html, header.html for navbar; footer.html for footer
  • Configurable via docs-config.json landing settings

Improvements

  • Fixed file extension filtering in sync pipeline

v1.1.0

10 Feb 21:49

Choose a tag to compare

What's New

Added

  • Nuxt Framework Support: Full Nuxt template support in the CLI
    • Framework detection via nuxt.config.ts/nuxt.config.js or nuxt dependency
    • Dev server with --port flag, build with .output/public output directory
    • Pagefind search indexing for Nuxt static builds

Fixed

  • Scaffold Directory: Moved dev-project directory from /tmp/.lito to ~/.lito/dev-project to fix bundler resolution issues (e.g. Turbopack failing to resolve node_modules from /tmp)

Full Changelog: v1.0.0...v1.1.0