skills.rest
litestar-org
litestar-orgOFFICIAL
Explore all skills by this author →
Website𝕏@LitestarAPIGitHub

litestar-build

Configure Litestar fullstack builds with Vite assets, PyApp binaries, and GitHub Actions CI/CD.

13|Updated Apr 15, 2026
Search Tags:#github-actions#ci-cd#hatchling#litestar#wheel-build#pyapp#frontend-bundling
One-click install
npx skills add https://github.com/litestar-org/litestar-skills --skill litestar-build
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: litestar-build
Source: https://github.com/litestar-org/litestar-skills/tree/main/plugins/litestar/skills/litestar-build
Command: npx skills add https://github.com/litestar-org/litestar-skills --skill litestar-build

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about litestar-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bundle Vite frontend assets into a Python wheel for a Litestar fullstack app?▼

To bundle Vite assets into a Litestar Python wheel, configure the Vite outDir to output inside your package and use Hatchling bundling with force-include or ignore-vcs to embed the assets directly, creating self-contained, atomic, version-aligned releases.

Can I build offline-capable PyApp binaries for Litestar applications?▼

Yes, you can build offline-capable PyApp binaries for Litestar applications by using advanced custom-install-dir patterns with hatch-binary workflows, enabling single-file distribution for air-gapped or corporate environments.

What is the best way to set up GitHub Actions CI/CD for multi-platform Litestar releases?▼

The best way to set up GitHub Actions CI/CD for Litestar releases is to use reusable workflow patterns for test matrices and multi-platform binary builds, automating artifact publishing via a single tag push while avoiding pitfalls like missing placeholder asset directories.

Does Litestar PyApp binary packaging support glibc 2.17+ for portable Linux artifacts?▼

Yes, Litestar PyApp binary packaging supports glibc 2.17+ compatibility to produce portable Linux artifacts, ensuring your built binaries run reliably across a wide range of target Linux distributions without encountering glibc version conflicts.

Why does my Litestar wheel build break when including Vite or Bun frontend assets?▼

Litestar wheel builds often break with Vite or Bun frontend assets due to misconfigured asset paths, missing build steps, or unhandled VCS settings, which you can fix by properly configuring Hatchling bundling to embed the assets directly into the wheel.

Related Skills

Explore More Software Engineering Skills→
emilneuraz-aiemilneuraz-ai

python-packaging

Package Python projects with pyproject.toml and publish to PyPI.

Community
Advanced
doleval013doleval013

deploy

Automate production deployments via GitOps with GitHub Actions and ArgoCD.

Community
Advanced
neozenithneozenith
2

setup-fullstack

Automate fullstack web app setup with FastAPI and React frontends.

Community
Advanced
aRustyDevaRustyDev
1

python-packaging

Package Python projects into distributable artifacts and publish them to PyPI.

Community
Intermediate