# Description of Changes Fixes #5407. A one-column prefix scan on a multi-column btree index — e.g. `filter(1n)` on a `[u64, string]` index — panicked at runtime with `TypeError: serializeTerm is not a function` inside `serializeRange`. A bare scalar (or bare `Range`) has no `.length`, so in the multi-column `filter`/`delete` accessor `range.length === numColumns` was `undefined === 2` (falling into the range-scan branch), and inside `serializeRange`: - `prefix_elems = range.length - 1` → `NaN` (prefix loop skipped), - `serializeTerm = indexSerializers[range.length - 1]` → `indexSerializers[NaN]` → `undefined`, - `serializeTerm(writer, term)` → **`TypeError: serializeTerm is not a function`**. A bare scalar is the only *type-valid* way to express a one-column prefix on a multi-column index — `filter([1n])` is rejected by the generated types and `filter([1n, "x"])` is the full key — so there was previously **no** working way to do a one-column prefix scan. The fix normalizes a non-array `range` to a single-element array at the top of the multi-column `filter`/`delete` before reading `.length`, so a bare scalar or `Range` is treated as a one-column prefix and takes the range-scan branch correctly. The full two-column key path is unchanged and still takes the point-scan branch. To regression-test the pure-JS index accessor under vitest, `makeTableView` is now exported from `src/server/runtime.ts` (it is **not** re-exported from any public entry point), the host-injected `spacetime:sys@*` virtual modules are stubbed, and aliased in `vitest.config.ts`. # API and ABI breaking changes None. `makeTableView` is newly exported from `src/server/runtime.ts` but is not re-exported from any public entry point. The host ABI is unchanged. # Expected complexity level and risk 1 — a one-line input normalization on each of `filter`/`delete`, plus test-only scaffolding. No change to the full-key path or the host syscall arguments. # Testing - [x] `npx vitest run tests/index_prefix_filter.test.ts` — bare scalar, bare `Range`, full two-column key, and `delete()` all scan without throwing (4 passed). - [x] `npx vitest run` — full suite, 223 passed. - [x] `tsc -p tsconfig.build.json` and `prettier --check` clean. - [x] Reviewer: confirm the prefix-scan semantics against a real datastore (the unit test uses a stubbed host iterator that yields no rows).
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