Developer tools from Incremental Company

Build reactive, server-rendered apps with one cohesive stack.

Incremental Code packages are designed to work together end to end: last-act for reactive rendering, last-router for file-system routes, last-server for SSR, last-ui for reusable interface primitives, and last-host for shipping to code.incremental.co.

npm install @incremental-code/last-act @incremental-code/last-router @incremental-code/last-server @incremental-code/last-ui

A package-first stack for signals, routing, SSR, UI, and deployment.

Why this stack

Designed to feel consistent from the first component to production deploys.

Signals-first foundation

last-act keeps the core tiny and reactive, so the rest of the stack can stay simple and composable.

SSR by default

last-server and last-router render on the server first, then keep body state live on the client.

One cohesive toolkit

UI primitives, routing, hosting, and examples are designed to feel like one system instead of separate libraries.

Packages

The core Incremental Code toolbox.

Each package stands on its own, but the whole system is tuned around the same rendering model and developer workflow.

Framework

last-act

@incremental-code/last-act

A minimal signal-based framework with JSX-compatible rendering, hydration, effects, and tiny runtime cost.

import { html } from '@incremental-code/last-act';

Router

last-router

@incremental-code/last-router

An isomorphic file-system router that maps folders to routes and streams API updates into reactive page state.

src/[username]/page.js  ->  /:username

SSR server

last-server

@incremental-code/last-server

Zero-config local SSR with JSX and TSX support, built to mirror the routing and rendering model in production.

npx last-server src

UI toolkit

last-ui

@incremental-code/last-ui

Small, polished building blocks like Container, Grid, Card, Button, and Heading that render cleanly on the server.

import { Container, Card } from "@incremental-code/last-ui";

Workflow

Write plain files, render on the server, and keep the path to production straightforward.

Step 01

Author components with signals

Start with plain function components, native elements, and signal-backed state that stays easy to reason about.

import { html } from '@incremental-code/last-act';

Step 02

Map folders to routes

Colocate pages and data handlers so local development and production routing use the same file structure.

src/about/page.js  ->  /about

Step 03

Render locally, ship globally

Run the app with SSR in development, then push the same model to hosted environments without changing architecture.

npx last-server src && npx last-host push src