Closes: https://github.com/clockworklabs/SpacetimeDB/issues/4571 - The secondary issue specifically # Description of Changes - Added new `onSchedule` optional parameter for `reducers` and `procedures` as suggested by @cloutiertyler to move towards reactive reducers - Enforced at most one scheduled `reducer`/`procedure` per schedule table - Kept the existing `table({ scheduled })` path working - Moved `ScheduleAt` column tracking onto table metadata - Lets the new schedule API resolve schedule-at columns without relying on legacy table options - Kept `schedule.scheduleAtCol` for compatibility # Other Options Considered - Add new additive API `.schedule()` - Was the first implementation of this branch but was the wrong direction for the future - Rust-inspired schedule token/name handle - Closest conceptual match to Rust: table stores a schedule descriptor/name and the reducer binds the implementation separately - Avoids importing reducers from table definitions and could preserve type checking if the token carries the row type - Adds more API surface and abstraction, and needs careful design to avoid users managing fragile names manually - `scheduled: 'reducerName'` string/name in `table(...)` - Very simple and closest to the raw module-def storage model - Fully breaks the runtime import cycle - Loses compile-time signature checking unless paired with another checker/registration API, and typos become runtime/module validation errors - This basically is what we had before 2.0 # API and ABI breaking changes - Adds new TypeScript options to `.reducer()` and `.procedure()` for `onSchedule` - No intended breaking changes to existing `table({ scheduled })` behavior # Expected complexity level and risk 3 - Preserving legacy scheduled table behavior while changing how schedule metadata is assembled # Testing - [x] Added new tests to cover the legacy schedule and new registration - [x] Updated module-test-ts coverage to show both legacy and new reducer scheduling - [x] Ran a local throwaway test project to test before and after for both legacy + new api
SpacetimeDB Module Library and SDK
Overview
This repository contains both the SpacetimeDB module library and the TypeScript SDK for SpacetimeDB. The SDK allows you to interact with the database server from a client and applies type information from your SpacetimeDB server module.
Installation
The SDK is an NPM package, thus you can use your package manager of choice like NPM or Yarn, for example:
npm add spacetimedb
You can use the package in the browser, using a bundler like vite/parcel/rsbuild, in server-side applications like NodeJS, Deno, Bun, NextJS, Remix, and in Cloudflare Workers.
NOTE: For usage in NodeJS 18-21, you need to install the
undicipackage as a peer dependency:npm add spacetimedb undici. Node 22 and later are supported out of the box.
Usage
In order to connect to a database you have to generate module bindings for your database.
import { DbConnection, tables } from './module_bindings';
const connection = DbConnection.builder()
.withUri('ws://localhost:3000')
.withDatabaseName('MODULE_NAME')
.onDisconnect(() => {
console.log('disconnected');
})
.onConnectError(() => {
console.log('client_error');
})
.onConnect((connection, identity, _token) => {
console.log(
'Connected to SpacetimeDB with identity:',
identity.toHexString()
);
connection.subscriptionBuilder().subscribe(tables.player);
})
.withToken('TOKEN')
.build();
If you need to disconnect the client:
connection.disconnect();
Typically, you will use the SDK with types generated from SpacetimeDB module. For example, given a table named Player you can subscribe to player updates like this:
connection.db.player.onInsert((ctx, player) => {
console.log(player);
});
Given a reducer called CreatePlayer you can call it using a call method:
connection.reducers.createPlayer();
React Usage
This module also includes React hooks to subscribe to tables under the spacetimedb/react subpath. The React integration is fully compatible with React StrictMode and handles the double-mount behavior correctly (only one WebSocket connection is created).
In order to use SpacetimeDB React hooks in your project, first add a SpacetimeDBProvider at the top of your component hierarchy:
const connectionBuilder = DbConnection.builder()
.withUri('ws://localhost:3000')
.withDatabaseName('MODULE_NAME')
.withLightMode(true)
.onDisconnect(() => {
console.log('disconnected');
})
.onConnectError(() => {
console.log('client_error');
})
.onConnect((conn, identity, _token) => {
console.log(
'Connected to SpacetimeDB with identity:',
identity.toHexString()
);
conn.subscriptionBuilder().subscribe(tables.player);
})
.withToken('TOKEN');
ReactDOM.createRoot(document.getElementById('root')!).render(
<React.StrictMode>
<SpacetimeDBProvider connectionBuilder={connectionBuilder}>
<App />
</SpacetimeDBProvider>
</React.StrictMode>
);
One you add a SpacetimeDBProvider to your hierarchy, you can use SpacetimeDB React hooks in your render function:
function App() {
const conn = useSpacetimeDB<DbConnection>();
const { rows: messages } = useTable<DbConnection, Message>('message');
...
}
SolidJS Usage
This module also includes SolidJS primitives to subscribe to tables under the spacetimedb/solid subpath. The SolidJS integration uses Solid's fine-grained reactivity system (createSignal, createStore, createMemo, createComputed) for optimal rendering performance. Reactive updates are scoped to only the data that actually changed.
In order to use SpacetimeDB SolidJS primitives in your project, first add a SpacetimeDBProvider at the top of your component hierarchy:
import { SpacetimeDBProvider } from 'spacetimedb/solid';
import { DbConnection, tables } from './module_bindings';
const connectionBuilder = DbConnection.builder()
.withUri('ws://localhost:3000')
.withDatabaseName('MODULE_NAME')
.withLightMode(true)
.onDisconnect(() => {
console.log('disconnected');
})
.onConnectError(() => {
console.log('client_error');
})
.onConnect((conn, identity, _token) => {
console.log(
'Connected to SpacetimeDB with identity:',
identity.toHexString()
);
conn.subscriptionBuilder().subscribe(tables.player);
})
.withToken('TOKEN');
render(
() => (
<SpacetimeDBProvider connectionBuilder={connectionBuilder}>
<App />
</SpacetimeDBProvider>
),
document.getElementById('root')!
);
Once you add a SpacetimeDBProvider to your hierarchy, you can use the SpacetimeDB SolidJS primitives in your components:
import {
useSpacetimeDB,
useTable,
useReducer,
useProcedure,
} from 'spacetimedb/solid';
function App() {
// Access the connection state (identity, token, connection error, etc.)
const conn = useSpacetimeDB();
// Subscribe to a table — returns a reactive store of rows and an isReady accessor
const [rows, isReady] = useTable(() => tables.message);
// Subscribe to a filtered view
const [onlineUsers, onlineReady] = useTable(
() => tables.user.where(r => r.online.eq(true)),
{
onInsert: row => console.log('User came online:', row),
onDelete: row => console.log('User went offline:', row),
}
);
// Call a reducer — queues calls made before the connection is ready
const sendMessage = useReducer(reducers.sendMessage);
// Call a procedure — queues calls made before the connection is ready
const getResult = useProcedure(procedures.getSomeResult);
return (
<div>
<Show when={isReady()} fallback={<p>Loading...</p>}>
<p>{rows.length} messages</p>
<For each={rows}>{row => <div>{row.text}</div>}</For>
</Show>
<button onClick={() => sendMessage('hello')}>Send</button>
</div>
);
}
Key differences from the React API:
useTabletakes a getter function() => Query<TableDef>instead of a plain value, so the query can be reactive and update when signals change.useTablereturns[rows, isReady]whererowsis a Solid reactive store andisReadyis an accessor function() => boolean.- The
enabledcallback option is a getter() => booleaninstead of a plain boolean, allowing it to depend on reactive state. useReduceranduseProcedurequeue calls made before the connection is ready and flush them once connected.
Developer notes
To run the tests, do:
pnpm build && pnpm test