preact-buildless-frontend
Build-less ESM Frontend
Create frontends that run directly in the browser using ES modules—no bundler, no build step.
Starter Template
Copy from assets/starter/ for a working baseline:
index.html— import map + module entryapp.js— Preact + signals + hash routingindex.css— CSS variables, dark mode
Run locally:
npx serve assets/starter # or python3 -m http.server 3000
Core Patterns
1. Import Maps
Use <script type="importmap"> to:
- Map bare specifiers (
preact) to CDN URLs - Map directory aliases (
@utils/) to local folders - Attach
?v=<version>for cache-busting
<script type="importmap">
{
"imports": {
"preact": "https://cdn.jsdelivr.net/npm/preact@10.24.3/dist/preact.module.js",
"@utils/": "./utils/",
"./app.js": "./app.js?v=1.0.0"
}
}
</script>
Generate this map dynamically (server middleware) or commit a static version.
2. CDN Imports
Import third-party ESM directly from CDN. Pin versions:
import { signal } from 'https://cdn.jsdelivr.net/npm/@preact/signals@1.3.0/dist/signals.module.js';
Prefer mapping through import map to keep source clean:
import { signal } from '@preact/signals'; // resolved via import map
3. Cache-Busting
Two approaches:
A) Versioned URLs (recommended):
- Append
?v=<git-sha|version|timestamp>to local.jsand.css - Set
Cache-Control: immutableheaders
B) ETag/Last-Modified:
- Keep stable URLs, let browser revalidate
For dynamic injection, rewrite index.html at serve time. For static hosting, commit versioned URLs manually.
4. Subpath Mounting
If served under a subpath (e.g., /app), use <base>:
<base href="/app/">
Ensures relative imports resolve correctly.
Structure
Minimal:
frontend/
index.html
index.css
app.js
Growing app:
frontend/
index.html
index.css
app.js # entry + router
state.js # signals/atoms
api.js # fetch helpers
components/
nav.js
pages/
home.js
settings.js
Configuration
Inject environment variables via global window.ENV (no build replacement).
index.html:
<script src="/config.js"></script>
<script type="module" src="./app.js"></script>
config.js:
window.ENV = {
API_URL: "https://api.example.com"
};
Exclude config.js from caching or generate at runtime.
Routing
Hash-based routing (no server config needed):
const route = signal(location.hash.slice(1) || '/');
window.addEventListener('hashchange', () => {
route.value = location.hash.slice(1) || '/';
});
// Links: <a href="#/about">About</a>
// Read: route.value === '/about'
For history API routing, the server must serve index.html for all routes.
Lazy Loading
Load features on demand:
button.onclick = async () => {
const { heavyFeature } = await import('./heavy.js');
heavyFeature();
};
Rule: if not needed for first paint, load lazily.
Error Handling
Wrap dynamic imports:
async function loadPage(name) {
try {
return await import(`./pages/${name}.js`);
} catch (e) {
console.error(`Failed to load ${name}:`, e);
return { default: () => html`<p>Failed to load page.</p>` };
}
}
Type Safety
Use JSDoc + jsconfig.json for full type checking without TypeScript build step.
jsconfig.json:
{ "compilerOptions": { "checkJs": true, "module": "ESNext" } }
Code usage:
/** @type {import('./types.js').User} */
const user = await api.getUser();
Performance
Startup:
- One
<script type="module">entry - Use
<link rel="modulepreload" href="...">for critical deps (fixes waterfall) - Import only what's needed for first paint
Rendering (with framework):
- Fine-grained reactivity (signals) over full re-renders
- Memoize expensive computations
Rendering (vanilla DOM):
- Event delegation on root
- Batch DOM writes (build fragment, insert once)
- Avoid layout thrash (don't interleave reads/writes)
CSS:
- CSS variables for theming
- Shallow selectors
- Avoid large frameworks
Security
Content Security Policy (CSP): Strict CSP blocks inline scripts. For inline import maps, use:
- Nonce:
<script type="importmap" nonce="...">(recommended) - Hash:
'sha256-...'of the script content
Allow CDNs in script-src:
Content-Security-Policy: script-src 'self' 'nonce-...' https://cdn.jsdelivr.net;
Deliverables
When asked to create a build-less frontend:
- Frontend folder with
index.html,index.css, entry JS - Import map with CDN deps + local modules
- (Optional) Server config for cache headers / HTML rewriting
Constraints
- No bundler, no transpilation
type="module"everywhere- Relative imports with
.jsextension (./utils.js) - Bare imports only if mapped in import map
Pitfalls
- Bare imports without map → browser error
- Import cycles → keep modules focused
- Missing
<base>→ broken imports on subpath - Eager imports → slow startup; use lazy
import() - Browser support → import maps need Chrome 89+, Firefox 108+, Safari 16.4+
Verification
After generating:
- Start server (
npx serveorpython3 -m http.server) - Open in browser, check console for errors
- Network panel: confirm
.jsloads astype="module" - If cache-busting: confirm
?v=...in URLs
More from av/skills
tinygrad
Deep learning framework development with tinygrad - a minimal tensor library with autograd, JIT compilation, and multi-device support. Use when writing neural networks, training models, implementing tensor operations, working with UOps/PatternMatcher for graph transformations, or contributing to tinygrad internals. Triggers on tinygrad imports, Tensor operations, nn modules, optimizer usage, schedule/codegen work, or device backends.
19run-llms
Comprehensive guide for setting up and running local LLMs using Harbor. Use when user wants to run LLMs locally, set up or troubleshoot Ollama, Open WebUI, llama.cpp, vLLM, SearXNG, Open Terminal, or similar local AI services. Covers full setup from Docker prerequisites through running models, per-service configuration, VRAM optimization, GPU troubleshooting, web search integration, code execution, profiles, tunnels, and advanced features. Includes decision trees for autonomous agent workflows and step-by-step troubleshooting playbooks.
16turso-db
Install, configure, and work with Turso DB — an in-process SQLite-compatible relational database engine written in Rust. Use when the user needs to (1) install Turso DB, (2) create or query databases with the tursodb CLI shell, (3) use Turso from JavaScript/Node.js via @tursodatabase/database, (4) work with vector search or embeddings in Turso, (5) set up full-text search with FTS indexes, (6) configure transactions including MVCC concurrent transactions, (7) enable encryption at rest, or (8) use Change Data Capture (CDC) for audit logging.
8boost-modules
Create custom modules for [Harbor Boost](https://github.com/av/harbor/tree/main/boost), an optimizing LLM proxy. Use when building Python modules that intercept/transform LLM chat completions—reasoning chains, prompt injection, structured outputs, artifacts, or custom workflows. Triggers on requests to create Boost modules, extend LLM behavior via proxy, or implement chat completion middleware.
8bugbash
Systematically explore and test any software project (CLI, API, Backend, Library, etc.) to find bugs, usability issues, and edge cases. Produces a structured report with full reproduction evidence (exact commands, inputs, logs, and tracebacks) for every issue.
5agent-integration-testing
Use when the user requests integration testing, feature validation, or test plan execution
4