What problem does it solve? Building a Litestar app with a bundled frontend often produces wheels that silently drop the compiled JavaScript and CSS, and shipping a single-file binary that works offline or on older Linux distros requires deep knowledge of PyApp, Hatchling, and cargo-zigbuild. This Skill codifies the exact build-side packaging patterns so wheels, onefile binaries, and GitHub Actions release pipelines work correctly the first time. ## Core Features & Use Cases - Self-contained wheel builds: Configure Vite/litestar-vite output directories inside the Python package and choose between Hatchling force-include or ignore-vcs = true so frontend assets, SQL migrations, and templates ship inside the wheel. - PyApp onefile binaries: Two flavors covered — simple hatch build --target binary for PyPI-connected users, and an advanced offline bundler using python-build-standalone, a patched PyApp app.rs install directory, and cargo zigbuild for glibc 2.17 compatibility. - GitHub Actions CI and release pipelines: Reusable test-matrix workflows, composite setup actions for pinned uv and Bun versions, and tag-triggered release workflows that build one wheel, matrix-compile per-platform binaries, and publish a GitHub release. - Use Case: You have a Litestar + React app and need to ship an air-gapped enterprise installer. Follow the advanced PyApp pattern to produce a ~500 MB onefile that extracts to ~/.myapp/runtime/ and passes a network-isolated distroless smoke test. ## Quick Start Ask the assistant to configure your Litestar project so the Vite build output lands inside the Python package and uv build --wheel produces a self-contained wheel with the frontend included.
