ResuxResumable web framework for Vue-like apps

Build server-rendered pages that ship HTML first, serialize state, and load client handler code only when users interact.

Get Started

Learn the Runtime

API Reference

HTML

HTML first, JS on demand

Resux renders HTML on the server, serializes route and component state, and imports handler modules only after an event is triggered.

SFC

Familiar .vue files

Use a focused Vue-like SFC subset with template, script setup, pages routing, layouts, and components.

Resumable state

useState and useAsyncData data is serialized into the payload so scopes can resume without whole-app hydration.

ROUTE

File routing

Add pages, dynamic params, catch-all routes, layouts, route middleware, and client-side navigation.

API

Server API included

Build API routes and request middleware with h3-backed helpers such as readBody, getQuery, and setHeader.

ISLAND

Vue islands when needed

Keep Resux components zero-default-hydration, then opt into Vue runtime islands for complex client widgets.

Install in one command

npx resuxjs@latest init my-app
cd my-app
npm install
npm run dev

@latest currently resolves to resuxjs@0.2.23 (checked on 2026-05-07).

A tiny Resux component

vue

<script setup lang="ts">
const count = useState('count', () => 0)

function increment() {
  count.value++
}
</script>

<template>
  <button @click="increment">
    Count: {{ count }}
  </button>
</template>

The server renders the button as HTML. The browser receives the serialized count state and a small delegated runtime. The handler chunk is loaded only when the button is clicked.

What should I read first?

New to Resux: start with What is Resux?, Core Concepts, and Getting Started.
Understanding the runtime: read Rendering Lifecycle and Resumability and Handlers.
Understanding where code belongs: use Execution Contexts, App Shell, Errors, and Public Files, and Security and Caching.
Building an app: read Project Structure, Routing, and Async Data.
Looking for exact APIs: jump to Composables and Globals and CLI.
Deploying: use Deployment and Docker Deployment.