htmx

htmx — access AJAX, CSS transitions, and SSE directly from HTML attributes.

FrontendSimple

Stack Components

Libraryhtmx 2.x

Why

Eliminates JS for common interactivity patterns, server-rendered HTML over the wire. JavaScript is used by 62% of developers per the Stack Overflow 2024 survey, and React holds 40% framework market share (State of JS 2024).

Vite replaced Webpack as the default bundler, cutting dev server startup from 30s to <1s.

When

Use for server-driven apps with partial page updates. Avoid for complex client state.

How

1. Add htmx via CDN script 2. Use hx-get/hx-post attributes 3. Target with hx-target 4. Swap with hx-swap

Example

<button hx-get="/users" hx-target="#list">Load Users</button> <div id="list"></div> // htmx — usage example import { htmx } from "fe2-htmx"; const result = await htmx({ input: "data" }); console.log(result);

Common Problems

⚠Flash of unstyled content — use hx-indicator for loading states
⚠CSRF tokens — include via hx-headers or meta tag
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use hx-swap='outerHTML' for full element replacement
✓Add hx-push-url for bookmarkable states
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is htmx and what projects is it for?

htmx — access AJAX, CSS transitions, and SSE directly from HTML attributes. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with htmx in 10 minutes?

Two steps: (1) Add htmx via CDN script; (2) Use hx-get/hx-post attributes. Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with htmx and how do I avoid it?

The most common pitfall is: Flash of unstyled content — use hx-indicator for loading states. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for htmx?

Best practices for htmx include: Use hx-swap='outerHTML' for full element replacement; Add hx-push-url for bookmarkable states; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use hx-swap='outerHTML' for full element replacement" — should be set up at project init to avoid costly rework later.

When should I NOT choose htmx?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). htmx shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.