litestar-build

What problem does it solve?

Litestar fullstack applications that bundle Vite/Bun frontend assets often face broken wheel builds, inconsistent CI pipelines, and fragile PyApp binary packaging due to misconfigured asset paths, missing build steps, or unhandled edge cases like glibc compatibility and offline distribution. This skill eliminates that guesswork with production-tested, canonical patterns from official Litestar reference apps.

Core Features & Use Cases

• Self-contained wheel builds: Guides configuring Vite outDir and Hatchling bundling (either force-include or ignore-vcs = true) to embed frontend assets directly into Python wheels for atomic, version-aligned releases.
• PyApp binary packaging: Covers both simple hatch-binary workflows for standard distribution and advanced offline, custom-install-dir patterns for air-gapped or corporate environments.
• GitHub Actions CI/CD: Provides reusable workflow patterns for test matrices, multi-platform binary builds, release automation, and artifact publishing, including guardrails for common pitfalls like missing placeholder asset directories and coverage upload conflicts.
• Use Case: A Litestar team shipping a fullstack React + Inertia.js app can use this skill to set up a build pipeline that produces a single self-contained wheel, builds PyApp binaries for Linux, macOS, and Windows, and automates releases via GitHub Actions with a single tag push.

Quick Start

Use the litestar-build skill to configure your Vite build to output inside your Python package, set up Hatchling to bundle frontend assets into your wheel, add a GitHub Actions release workflow that builds and publishes your wheel and PyApp binaries for all target platforms, and validate your build with the provided checklist before shipping.