Oxide

The backend unframework.

Ship a backend from the bundler you already use. Call the server from the client like a function.

// notes.server.ts
import { action } from "oxidejs";

export const create = action(async (title: string) => {
  return { id: crypto.randomUUID(), title };
});

// client.ts
import { create } from "./notes.server";

const note = await create("Ship Oxide");

Looks local. Runs on the server.

// vite.config.ts
import { defineConfig } from "vite";
import oxide from "oxidejs/vite";

export default defineConfig({
  plugins: [oxide()],
});

Vite or Rsbuild. Switch the import. Keep the rest.

bun add oxidejs tacho

It guides you. It doesn't frame you.

• Single bundle — One folder to deploy. A server, and a client if you have a page.
• Server actions — Wrap a *.server.ts export in action(), then import and call it from the client.
• Fetch or celld — Run the generated server on Node-compatible hosts, or emit a celld worker.

Packages

Package	Purpose
oxidejs	Turns Vite or Rsbuild into a backend. One plugin, one folder to deploy.
tacho	Typed JSON-RPC. The wire those actions ride on. Also usable on its own.

Need RPC without the plugin? Use tacho. typeof router is the client. The templates/tasks and templates/tasks-celld apps show fetch and celld deployments.

Docs · oxidejs · tacho

License

MIT © Ryuz