Blitsen

01 / Configure

Point Blitsen at built web output

Add one object to package.json. The build command stays yours; Blitsen consumes the directory it leaves behind.

{
  "blitsen": {
    "build": "vite build",
    "output": "dist",
    "name": "My App"
  }
}

Plain HTML needs no configuration: blitsen . opens the directory containing index.html.

02 / Run and build

Use the same output from first window to release

blitsen                       # build and open a native window
blitsen doctor dist           # check the built application
blitsen build                 # create a desktop executable

During development, point Blitsen at a running server such as http://localhost:5173 to keep its transforms and hot reload. Before release, run doctor against static output and test the exported artifact on every target platform.

03 / Know the boundary

A native runtime, not a general-purpose browser

1. 01

   Use built output

   Blitsen does not transpile source files or resolve bare npm imports. Vite, webpack or your existing tool must do that first.

2. 02

   Check compatibility

   The runtime implements a deliberate subset of browser APIs. Missing features are absent so feature detection works, and doctor reports what it can see.

3. 03

   Treat it as native software

   There is no browser sandbox, same-origin policy or permission prompt. Run only application code and content you trust.

04 / Reach the OS

Use native capabilities when the web has no answer

Package imports expose window controls, dialogs, clipboard formats, application directories and live operating-system readings.

import windowApi from "blitsen/window";

addEventListener("load", () => {
  windowApi.setSize?.(1024, 720);
});

Support varies by version and target, so native members are optional and feature detection is part of the API. Browse native APIs →

05 / Distribute

Build for Windows, macOS and Linux

Desktop exports embed reachable assets in one executable by default. Add platform metadata, connect your signing command, or cross-build for any of the six desktop targets. Every export includes Bun and the native renderer. Mobile support is deferred.

Packaging and release checklist →