Overview
| Area | What you get |
|---|---|
| Reactivity | A literal let in the --- block is browser state. $state, $derived and $effect in a plain <script>. Islands (client:visible, client:idle, client:media). Hot reload keeps $state. |
| AI and tokens | AGENTS.md and llms-full.txt hold the reference. wisp mcp serves it. A whole app takes under half the tokens of SvelteKit or Next.js (Tokens). |
| Rendering | Server rendering, streamed responses, {#await}. Prerendered pages, wisp build --static and --spa. |
| Data and forms | #[action] with validation, uploads, #[remote] functions, #[derive(Rest)] JSON APIs, a store for log files or any database. |
| Styling | Scoped CSS in <style>, Tailwind and Sass. |
| Tooling | wisp lsp (VS Code, Zed, tree-sitter, Prettier), wisp fmt, wisp check, wisp test, wisp test --browser. Devtools on Alt+Shift+W. |
| Deploy | One binary, wisp deploy init docker, wisp build --static, or wisp build --target cloudflare|deno|vercel|netlify|node|bun|lambda. wisp deploy init <host> writes a GitHub Actions workflow or a Fly, Render or Railway config. |
Speed
The first rule is zero cost on the request hot path. See Benchmarks. There is no unsafe code outside the Linux I/O drivers, the edge exports and the Windows Job Object in the CLI that ends wisp dev companions.
Docs
- Design: templates, routing, actions and the runtime.
- Browser code: scripts, directives, islands, stores and the router.
- APIs and platforms: JSON APIs, validation, auth, OpenAPI and testing.
- Deploying and Testing and mixing with Rust code.
- Examples: ten small apps, each with its files and code to read and a download. The repo also holds a demo app, a JSON API and Wisp inside axum.
The design rule is at the top of AGENTS.md. Until the GitHub repository opens, ask in the Discord. License: MIT.
Status
Wisp is a pre-release. The real release will be on GitHub, which we cannot use yet because GitHub suspended our account without notice. The source is at code.wispweb.dev and moves to GitHub and crates.io with 1.0. Security and hardening lists the tests, the fuzzing and what is not claimed.
A feature ships when it is fast (no cost for apps that do not use it), cheap (one line, file or attribute), durable (the build checks it, no runtime panics) and done (tests, an AGENTS.md entry, a docs section). Five phases have shipped:
- Compiler: scoped styles, source maps, TypeScript in scripts, accessibility warnings, public and private environment variables (
env.PUBLIC_X), Content Security Policy. - Developer experience:
wisp lsp,wisp fmt, hot reload that keeps state, devtools,wisp test --browser. - Rendering and routing: SPA mode (
const SSR: bool = false;), code loading on demand,#[remote], shallow routing, snapshots,const PRERENDER: bool = true;, trailing slash. - Content and assets: Markdown pages, image optimization, i18n, sitemap and robots.txt.
- Platform: service worker and PWA, web components (
{@element "x-card"}), third-party UI (wisp ui add, framework islands), observability (WISP_LOG=json,/_wisp/metrics, OpenTelemetry).
Images use a pinned cwebp (sha256 checked, $WISP_CWEBP override). If it is missing, the build warns and serves the original. Markdown uses pulldown-cmark at build time only. Wisp supports i18n, but its own docs stay English.
Is This Page Useful?