Expand description
Local build strategies.
A BuildStrategy runs a project’s build locally and reports where the
shippable output is, as a BuildArtifact. Transport (see
crate::transport) takes it from there. Keeping “build” and “ship”
separate is what lets the same engine drive a local build, a CI build, or a
server-side build without the strategies knowing which.
Structs§
- Build
Artifact - What a build produced and where to ship it from.
- Svelte
KitBuild - A SvelteKit build using
@sveltejs/adapter-static: install dependencies, run<package_manager> run build, and ship the adapter’s output directory (buildby default). - Vite
SpaBuild - A Vite / SPA build: run
<package_manager> buildin the project directory and ship its output directory (e.g.dist).
Enums§
- Svelte
KitAdapter - Which SvelteKit adapter a project declares in its
package.json.
Traits§
- Build
Strategy - Builds a project locally into a
BuildArtifact.