Skip to main content
Framework adapters provide framework-specific defaults and optimizations for common frontend frameworks.

Overview

Adapters are convenience wrappers that apply framework-specific best practices:

Available Adapters

React

Optimized for React applications with Vite. Defaults:
  • Manifest: .vite/manifest.json
  • Output directory: dist
Example:

Vue

Optimized for Vue 3 applications with Vite. Defaults:
  • Manifest: .vite/manifest.json
  • Output directory: dist
Example:

Svelte

Optimized for Svelte applications with Vite. Defaults:
  • Manifest: .vite/manifest.json
  • Output directory: dist
Example:

SvelteKit

Optimized for SvelteKit with static adapter. Defaults:
  • Output directory: build
  • Index: index.html
Example:

Solid

Optimized for Solid.js with Vite. Defaults:
  • Manifest: .vite/manifest.json
  • Output directory: dist
Example:

Astro

Optimized for Astro with static output. Defaults:
  • Output directory: dist
  • Index: index.html
Example:

Angular

Optimized for Angular applications. Defaults:
  • Output directory: dist/app-name/browser
  • Index: index.html
Example:

Using Adapters

Basic Usage

With Embedded FS

Custom Configuration

Adapters still accept all standard options:

When to Use Adapters

Use adapters when:
  • Using standard framework setup
  • Want framework-specific optimizations
  • Prefer convention over configuration
Use frontend.WithOptions when:
  • Custom build configuration
  • Non-standard directory structure
  • Need full control over options

Creating Custom Adapters

You can create your own adapters:
Use:

Adapter Comparison

Next Steps

API Reference

Complete API documentation

Configuration

All configuration options

Framework Guides

Framework-specific guides