Zenbu.js is a JavaScript framework for building hackable software.

Documentation   ·   DeepWiki   ·   Discord   ·   Try the demo →

Get started in 5 seconds

npx create-zenbu-app

1. Coding agents can generate and customize software on demand for a specific use case. A hackable app gives them full access to do that.

2. Letting people modify your app means more directions get explored than you could reach on your own.

3. Extensible code tends to be more maintainable, because it’s already written to be changed.

Users can modify Zenbu apps in 2 ways:

When a Zenbu app is built for production, there is no TypeScript compilation or bundling step. The same source code you wrote in development will be downloaded by the user and stored in ~/.zenbu/<app-name>. When the app launches, it discovers the app code, dynamically compiles it, and runs the JavaScript using Electron's Node.js runtime.

All the source code in this directory is being watched for changes. When there is a change, the app will re-run affected code nearly instantly (also known as hot reloading). Hot reloading is implemented both in the main process and the renderer process.

The codebase stored inside ~/.zenbu/<app-name> is tracked by git. This makes it possible for a user to edit the source code without losing changes when the application code gets updated. The git repo is linked to a remote repository owned by the developer, so updates are represented as running git pull on the user's device.

Editing the raw source code of the application can be risky. If a user and the developer have conflicting edits, the user needs to spend time merging changes. This motivates plugins - a way to inject code into the application that can modify behavior without editing the raw source code.

Plugins run in the same process as the application code and get access to the same APIs. This means any feature written in the main app could be written as a plugin.

When you write an app in Zenbu your code is extensible by default, so plugins can extend it without you designing a plugin API up front. For more complex parts of your app that need a richer extension model, you can define your own on top.

Plugins hot reload just like application code, because application code is itself implemented as a plugin.

Zenbu.js is not a one-size-fits-all model for building extensible applications. It provides a general-purpose way to load external code, with primitives for hot reloading, sharing state, and extending UI. For more complex behavior that isn't covered by Zenbu's architecture, you'll need your own conventions and systems for how that part gets extended, defined inside your Zenbu app.

• Non sandboxed out-of-process plugins
• Improved sandboxing controls for plugins
• Performance work
• Migrate custom node HMR to Vite's environments API
• HMR for node_modules, advice, and content scripts
• Windows and Linux support
• Automatic CLI per app
• Git-based auto updater
• WebRTC adapter for zenrpc and kyju (the database)
• Add optimized production mode that pre-compiles and bundles the typescript to javascript (would opt project out of allowing its source code edited at runtime by user)
• Support for running outside of electron (local node.js process + website, within tauri, natively on the web)
• Plugin devtools

Zenbu.js is a project from Zenbu Labs.

Read the docs →