CLI
The coralite binary is the only tool you need: develop, build, validate, and fix the workspace.
Commands
coralite dev # Development server with incremental rebuilds
coralite build # Production build into dist/
coralite test # Testing server (deterministic build for E2E)
coralite check # Unified validation across components, pages, plugins
coralite fix # Apply safe auto-fixes across the workspace
coralite init-agent # Scaffold AGENTS.md and AI IDE config aliases
Granular validators remain available when you want to scope a pass:
coralite validate-components
coralite validate-pages
coralite validate-plugins
Shared Build Flags
dev, test, and build accept the same options:
coralite build \
--clean # Clear the output directory first
--verbose # Verbose logging
--no-incremental # Rebuild every page and component
--assets pkg:path:dest # Copy static assets during build
Validation Options
coralite check reports AST diagnostics and TypeScript errors together. Use the filters to focus on one concern in CI or in an editor loop.
coralite check --only-failed # Only files with errors or warnings
coralite check --code E201 E203 # Filter by diagnostic code
coralite check --status failed # Filter by outcome
coralite check --format json # Machine-readable output
coralite check --no-types # Skip TypeScript, AST rules only
coralite check --strict # Treat warnings and unused code as failures
Auto-Fixes
coralite fix applies only safe transformations; preview them with --dry-run before writing. Interactive mode lets you accept each fix individually.
coralite fix --dry-run # Preview every change
coralite fix --code W402 # Fix one diagnostic class
coralite fix --migrate-pages # Upgrade legacy definePage config to flat exports
Configuration Discovery
Every command resolves coralite.config.js from the current directory upward. The resolved config supplies pages, components, fixtures, public, output, styles, store, and plugins, so no command needs path arguments in a standard project.
import { defineConfig } from 'coralite'
export default defineConfig({
public: 'public',
output: 'dist',
pages: 'src/pages',
components: 'src/components'
})
check exits non-zero when any error is reported, which makes it a drop-in CI gate. Add --strict to fail on warnings as well.