@livestore/livestore 0.4.0-dev.21 → 0.4.0-dev.23

package/docs/patterns/encryption/index.md

@@ -1,6 +0,0 @@
-# Encryption
-
-LiveStore doesn't yet support encryption but might in the future.
-See [this issue](https://github.com/livestorejs/livestore/issues/70) for more details.
-
-For now you can implement encryption yourself e.g. by encrypting the events using a custom Effect Schema definition which applies a encryption transformation to the events.

package/docs/patterns/external-data/index.md

@@ -1,5 +0,0 @@
-# External data
-
-LiveStore doesn't provide any built-in functionality to deal with external data. However, LiveStore was designed with this use case in mind (e.g. Overtone integrates with lots of external data like Spotify, ...). One way to deal with external data is to also model it as an event log and materialize it into LiveStore state as well.
-
-(If you're interested in learning more about the solution we're using for Overtone, get in touch.)

package/docs/patterns/file-management/index.md

@@ -1,11 +0,0 @@
-# File management
-
-LiveStore doesn't have built-in support for file management but it's easy to use LiveStore alongside existing file storage solutions (e.g. S3).
-
-The basic idea is to store the file metadata (e.g. url, name, size, type) in LiveStore and the file content separately.
-
-## Example
-
-```ts
-// TODO (contribution welcome)
-```

package/docs/patterns/file-structure/index.md

@@ -1,14 +0,0 @@
-# File structure
-
-While there are no strict requirements/conventions for how to structure your project (files, folders, etc), a common pattern is to have a `src/livestore` folder which contains all the LiveStore related code.
-
-```
-src/
-	livestore/
-		index.ts # re-exports everything
-		schema.ts # schema definitions
-		queries.ts # query definitions
-		events.ts # event definitions
-		...
-	...
-```

package/docs/patterns/list-ordering/index.md

@@ -1,369 +0,0 @@
-# List Ordering
-
-Fractional indexing enables conflict-free list ordering in distributed systems by assigning string-based position values that maintain lexicographic order. This makes it ideal for implementing drag-and-drop reordering in LiveStore applications where multiple clients may reorder items concurrently.
-
-To understand how the algorithm works, see these visual and interactive explanations:
-- [CRDT Fractional Indexing](https://madebyevan.com/algos/crdt-fractional-indexing/) by Evan Wallace - Visual explanation of the algorithm
-- [Implementing Fractional Indexing](https://observablehq.com/@dgreensp/implementing-fractional-indexing) by David Greenspan - Interactive notebook walkthrough
-
-## Why Fractional Indexing?
-
-Traditional numeric ordering (1, 2, 3...) requires renumbering multiple items when inserting or reordering, which creates conflicts in distributed systems. Fractional indexing solves this by:
-
-- Generating position values that can always be inserted between any two existing positions
-- Using lexicographic string ordering that works naturally with SQL `ORDER BY`
-- Eliminating the need for coordination between clients when reordering
-- Avoiding cascading updates when inserting items
-
-For example, inserting a new item between positions "a0" and "b0" generates "aV", which sorts correctly without modifying existing items.
-
-## Installation
-
-Install the `fractional-indexing` package from [Rocicorp](https://github.com/rocicorp/fractional-indexing) (the same team behind Replicache):
-
-```bash
-pnpm install fractional-indexing
-```
-
-## Schema Design
-
-Define a text column to store the fractional index and add a database index for efficient ordering:
-
-## `patterns/list-ordering/schema.ts`
-
-```ts filename="patterns/list-ordering/schema.ts"
-
-export const task = State.SQLite.table({
-  name: 'task',
-  columns: {
-    id: State.SQLite.integer({ primaryKey: true }),
-    title: State.SQLite.text({ default: '' }),
-    completed: State.SQLite.integer({ default: 0 }),
-    /** Fractional index for ordering tasks in the list */
-    order: State.SQLite.text({ nullable: false, default: '' }),
-  },
-  indexes: [
-    /** Index for efficient ordering queries */
-    { name: 'task_order', columns: ['order'] },
-  ],
-  deriveEvents: true,
-})
-
-export type Task = typeof task.Type
-
-export const tables = { task }
-```
-
-The `order` column stores string values like "a0", "a1", "aV" that maintain lexicographic ordering. Adding a database index on this column ensures efficient queries when retrieving ordered lists.
-
-## Creating Ordered Items
-
-Use `generateKeyBetween(a, b)` to generate position values when creating new items:
-
-## `patterns/list-ordering/create-item.ts`
-
-```ts filename="patterns/list-ordering/create-item.ts"
-
-declare const store: Store
-
-/** Create a new task at the end of the list */
-export const createTaskAtEnd = (title: string) => {
-  // Get the highest order value
-  const highestOrder = store.query(tables.task.select('order').orderBy('order', 'desc').limit(1))[0] ?? null
-
-  // Generate new order after the highest
-  const order = generateKeyBetween(highestOrder, null)
-
-  // Commit the event
-  store.commit(events.createTask({ title, order }))
-
-  return order
-}
-
-/** Create a new task at the beginning of the list */
-export const createTaskAtStart = (title: string) => {
-  // Get the lowest order value
-  const lowestOrder = store.query(tables.task.select('order').orderBy('order', 'asc').limit(1))[0] ?? null
-
-  // Generate new order before the lowest
-  const order = generateKeyBetween(null, lowestOrder)
-
-  store.commit(events.createTask({ title, order }))
-
-  return order
-}
-
-/** Create the very first task in an empty list */
-export const createFirstTask = (title: string) => {
-  // When the list is empty, use a simple default value
-  const order = 'a1'
-
-  store.commit(events.createTask({ title, order }))
-
-  return order
-}
-```
-
-### `patterns/list-ordering/events.ts`
-
-```ts filename="patterns/list-ordering/events.ts"
-
-export const events = {
-  createTask: Events.synced({
-    name: 'v1.CreateTask',
-    schema: Schema.Struct({
-      title: Schema.String,
-      order: Schema.String,
-    }),
-  }),
-  updateTaskOrder: Events.synced({
-    name: 'v1.UpdateTaskOrder',
-    schema: Schema.Struct({
-      id: Schema.Number,
-      order: Schema.String,
-    }),
-  }),
-}
-```
-
-### `patterns/list-ordering/schema.ts`
-
-```ts filename="patterns/list-ordering/schema.ts"
-
-export const task = State.SQLite.table({
-  name: 'task',
-  columns: {
-    id: State.SQLite.integer({ primaryKey: true }),
-    title: State.SQLite.text({ default: '' }),
-    completed: State.SQLite.integer({ default: 0 }),
-    /** Fractional index for ordering tasks in the list */
-    order: State.SQLite.text({ nullable: false, default: '' }),
-  },
-  indexes: [
-    /** Index for efficient ordering queries */
-    { name: 'task_order', columns: ['order'] },
-  ],
-  deriveEvents: true,
-})
-
-export type Task = typeof task.Type
-
-export const tables = { task }
-```
-
-Key patterns:
-- `generateKeyBetween(highest, null)` - Append to end of list
-- `generateKeyBetween(null, lowest)` - Prepend to start of list
-- Use `"a1"` as a simple default for the first item in an empty list
-
-## Reordering Items
-
-Handle drag-and-drop by generating a new position between the target boundaries:
-
-## `patterns/list-ordering/reorder.ts`
-
-```ts filename="patterns/list-ordering/reorder.ts"
-
-declare const store: Store
-
-/**
- * Reorder a task by moving it between two other tasks
- *
- * @param taskId - The task to reorder
- * @param beforeOrder - The order value of the task that will be before this one (null if moving to end)
- * @param afterOrder - The order value of the task that will be after this one (null if moving to start)
- */
-export const reorderTask = (taskId: number, beforeOrder: string | null, afterOrder: string | null) => {
-  // Generate a new fractional index between the two positions
-  const newOrder = generateKeyBetween(beforeOrder, afterOrder)
-
-  // Commit the update event
-  store.commit(events.updateTaskOrder({ id: taskId, order: newOrder }))
-
-  return newOrder
-}
-
-/**
- * Handle drag-and-drop reordering
- *
- * This is a more complete example showing how to handle drag-and-drop
- * with proper boundary checks.
- */
-export const handleDragDrop = (draggedTaskId: number, targetTaskId: number, dropPosition: 'before' | 'after') => {
-  const before = dropPosition === 'before'
-
-  // Get the target task's order
-  const targetOrder = store.query(tables.task.select('order').where({ id: targetTaskId }).first({ behaviour: 'error' }))
-
-  // Find the nearest task in the drop direction
-  const nearestOrder =
-    store.query(
-      tables.task
-        .select('order')
-        .where({
-          order: { op: before ? '>' : '<', value: targetOrder },
-        })
-        .orderBy('order', before ? 'asc' : 'desc')
-        .limit(1),
-    )[0] ?? null
-
-  // Generate new order between target and nearest
-  const newOrder = generateKeyBetween(before ? targetOrder : nearestOrder, before ? nearestOrder : targetOrder)
-
-  // Commit the update
-  store.commit(events.updateTaskOrder({ id: draggedTaskId, order: newOrder }))
-
-  return newOrder
-}
-```
-
-### `patterns/list-ordering/events.ts`
-
-```ts filename="patterns/list-ordering/events.ts"
-
-export const events = {
-  createTask: Events.synced({
-    name: 'v1.CreateTask',
-    schema: Schema.Struct({
-      title: Schema.String,
-      order: Schema.String,
-    }),
-  }),
-  updateTaskOrder: Events.synced({
-    name: 'v1.UpdateTaskOrder',
-    schema: Schema.Struct({
-      id: Schema.Number,
-      order: Schema.String,
-    }),
-  }),
-}
-```
-
-### `patterns/list-ordering/schema.ts`
-
-```ts filename="patterns/list-ordering/schema.ts"
-
-export const task = State.SQLite.table({
-  name: 'task',
-  columns: {
-    id: State.SQLite.integer({ primaryKey: true }),
-    title: State.SQLite.text({ default: '' }),
-    completed: State.SQLite.integer({ default: 0 }),
-    /** Fractional index for ordering tasks in the list */
-    order: State.SQLite.text({ nullable: false, default: '' }),
-  },
-  indexes: [
-    /** Index for efficient ordering queries */
-    { name: 'task_order', columns: ['order'] },
-  ],
-  deriveEvents: true,
-})
-
-export type Task = typeof task.Type
-
-export const tables = { task }
-```
-
-The `generateKeyBetween` function automatically creates a string value that sorts lexicographically between the two boundary positions. Pass `null` to represent the start or end of the list.
-
-## Querying Ordered Lists
-
-Query items using standard SQL ordering on the fractional index column:
-
-## `patterns/list-ordering/query.ts`
-
-```ts filename="patterns/list-ordering/query.ts"
-
-declare const store: Store
-
-/**
- * Query tasks in their proper order
- *
- * The fractional index values maintain lexicographic ordering,
- * so we can simply order by the 'order' column.
- */
-export const getOrderedTasks = () => {
-  return store.query(tables.task.select().orderBy('order', 'asc'))
-}
-
-/**
- * Get the highest order value (for appending new items)
- */
-export const getHighestOrder = (): string | null => {
-  const order = store.query(tables.task.select('order').orderBy('order', 'desc').limit(1))[0]
-
-  return order ?? null
-}
-
-/**
- * Get the lowest order value (for prepending new items)
- */
-export const getLowestOrder = (): string | null => {
-  const order = store.query(tables.task.select('order').orderBy('order', 'asc').limit(1))[0]
-
-  return order ?? null
-}
-```
-
-### `patterns/list-ordering/schema.ts`
-
-```ts filename="patterns/list-ordering/schema.ts"
-
-export const task = State.SQLite.table({
-  name: 'task',
-  columns: {
-    id: State.SQLite.integer({ primaryKey: true }),
-    title: State.SQLite.text({ default: '' }),
-    completed: State.SQLite.integer({ default: 0 }),
-    /** Fractional index for ordering tasks in the list */
-    order: State.SQLite.text({ nullable: false, default: '' }),
-  },
-  indexes: [
-    /** Index for efficient ordering queries */
-    { name: 'task_order', columns: ['order'] },
-  ],
-  deriveEvents: true,
-})
-
-export type Task = typeof task.Type
-
-export const tables = { task }
-```
-
-Since fractional index values maintain lexicographic ordering, you can use simple `ORDER BY` clauses without special handling.
-
-## Best Practices
-
-- **Use text/string columns** - Fractional index values are strings, not numbers
-- **Add database indexes** - Index the order column for efficient queries
-- **Validate lexicographic ordering** - Ensure your sorting logic uses standard string comparison, not locale-aware comparison (avoid `String.prototype.localeCompare()`)
-- **Handle empty lists** - Use a simple default like `"a1"` for the first item
-- **Consider bulk operations** - For creating multiple items at once, use `generateNKeysBetween(a, b, n)` from the same package
-
-## Real-World Example
-
-The [web-linearlite example](https://github.com/livestorejs/livestore/tree/dev/examples/web-linearlite) demonstrates fractional indexing for Kanban board ordering. It shows:
-- Schema definition with `kanbanorder` column
-- Creating issues with proper ordering
-- Drag-and-drop reordering across columns
-- Querying issues in order by status
-
-Check `examples/web-linearlite/src/livestore/schema/issue.ts` for the schema and `examples/web-linearlite/src/components/column.tsx` for the drag-and-drop implementation.
-
-## How It Works
-
-Fractional indexing generates position strings that always allow insertion between any two positions:
-
-```
-Initial:  a0    a1    a2
-Insert between a0 and a1: a0V (sorts: a0 < a0V < a1)
-Insert between a0V and a1: a0n (sorts: a0 < a0V < a0n < a1)
-```
-
-The algorithm ensures:
-- Position strings stay reasonably short
-- No coordination needed between clients
-- Conflicts resolve naturally through lexicographic ordering
-- Works seamlessly with LiveStore's event sourcing model
-
-For more details on the algorithm, see the [fractional-indexing documentation](https://github.com/rocicorp/fractional-indexing).

package/docs/patterns/offline/index.md

@@ -1,32 +0,0 @@
-# Offline support
-
-- LiveStore supports offline data management out of the box. In order to make your app work fully offline, you might need to also consider the following:
-  - Design your app in a way to treat the network as an optional feature (e.g. when relying on other APIs / external data)
-  - Use service workers to cache assets locally (e.g. images, videos, etc.)
-
-## Tracking connectivity
-
-Use `store.networkStatus` to react to connectivity transitions. The subscribable emits every time the sync backend connection flips or the devtools latch simulates an offline state.
-
-## `patterns/offline/tracking-connectivity.ts`
-
-```ts filename="patterns/offline/tracking-connectivity.ts"
-
-declare const store: Store
-
-// ---cut---
-
-const status = await store.networkStatus.pipe(Effect.runPromise)
-if (status.isConnected === false) {
-  console.warn('Sync backend offline since', new Date(status.timestampMs))
-}
-
-await store.networkStatus.changes.pipe(
-  Stream.tap((next) => Effect.sync(() => console.log('network status updated', next))),
-  Stream.runDrain,
-  Effect.scoped,
-  Effect.runPromise,
-)
-```
-
-When devtools close the sync latch to simulate an offline client, `status.devtools.latchClosed` is `true`, allowing you to differentiate between real and simulated outages. Remember to dispose of long-lived subscriptions using the Effect scope you already manage for your runtime.

package/docs/patterns/orm/index.md

@@ -1,18 +0,0 @@
-# ORM
-
-- LiveStore has a built-in query builder which should be sufficient for most simple use cases.
-- You can always fall back to using raw SQL queries if you need more complex queries.
-- As long as the ORM allows supports synchronously generating SQL statements (and binding parameters), you should be able to use it with LiveStore.
-- Supported ORMs:
-  - [Knex](https://knexjs.org/)
-	- [Kysely](https://kysely.dev/)
-  - [Drizzle](https://orm.drizzle.team/)
-  - [Objection.js](https://vincit.github.io/objection.js/)
-- Unsupported ORMs:
-  - [Prisma](https://www.prisma.io/) (because it's async)
-
-## Example
-
-```ts
-// TODO (contribution welcome)
-```

package/docs/patterns/presence/index.md

@@ -1,11 +0,0 @@
-# Presence
-
-LiveStore doesn't yet have any built-in presence functionality (e.g. to track online/offline users).
-
-Common presence use cases are:
-- Track which users are online / in a room
-- Track which users are typing (e.g. in a chat)
-- Text cursor (similar to Google Docs)
-- Cursor movements (similar to Figma)
-
-For now it's recommend to implement presence functionality in your application or use a third party service (e.g. Liveblocks).

package/docs/patterns/rich-text-editing/index.md

@@ -1,11 +0,0 @@
-# Rich text editing
-
-LiveStore doesn't yet have any built-in support for rich text editing. It's currently recommended to use a purpose-built library (e.g. [Yjs](https://yjs.dev/) or [Automerge](https://automerge.org/)) for this use case in combination with LiveStore.
-
-The idea here is to reference the rich text document from within LiveStore's event log and sync both in parallel.
-
-## Example
-
-```ts
-// TODO
-```

package/docs/patterns/server-side-clients/index.md

@@ -1,97 +0,0 @@
-# Server-side clients
-
-You can also use LiveStore on the server side e.g. via the `@livestore/adapter-node` adapter. This allows you to:
-- have an up-to-date server-side SQLite database (read model)
-- react to events / state changes on the server side (e.g. to send emails/push notifications)
-- commit events on the server side (e.g. for sensitive/trusted operations)
-
-<ServerSideClientDiagram />
-
-Note about the schema: While the `events` schema needs to be shared across all clients, the `state` schema can be different for each client (e.g. to allow for a different SQLite table design on the server side).
-
-## Example
-
-<Tabs>
-  <TabItem label="main.ts">
-
-## `reference/syncing/server-side-clients/main.ts`
-
-```ts filename="reference/syncing/server-side-clients/main.ts"
-/** biome-ignore-all lint/correctness/noUnusedVariables: docs snippet keeps inline setup */
-// ---cut---
-
-const adapter = makeAdapter({
-  storage: { type: 'fs', baseDirectory: 'tmp' },
-  sync: { backend: makeWsSync({ url: 'ws://localhost:8787' }), onSyncError: 'shutdown' },
-})
-
-const store = await createStorePromise({
-  adapter,
-  schema,
-  storeId: 'test',
-  syncPayload: { authToken: 'insecure-token-change-me' },
-})
-
-const todos = store.query(tables.todos.where({ completed: false }))
-```
-
-### `reference/syncing/server-side-clients/schema.ts`
-
-```ts filename="reference/syncing/server-side-clients/schema.ts"
-
-const events = {}
-
-const tables = {
-  todos: State.SQLite.table({
-    name: 'todos',
-    columns: {
-      id: State.SQLite.text({ primaryKey: true }),
-      text: State.SQLite.text(),
-      completed: State.SQLite.boolean({ default: false }),
-    },
-  }),
-}
-
-const state = State.SQLite.makeState({ tables, materializers: {} })
-
-export const schema = makeSchema({ events, state })
-
-export { tables }
-```
-
-</TabItem>
-  <TabItem label="schema.ts">
-
-## `reference/syncing/server-side-clients/schema.ts`
-
-```ts filename="reference/syncing/server-side-clients/schema.ts"
-
-const events = {}
-
-const tables = {
-  todos: State.SQLite.table({
-    name: 'todos',
-    columns: {
-      id: State.SQLite.text({ primaryKey: true }),
-      text: State.SQLite.text(),
-      completed: State.SQLite.boolean({ default: false }),
-    },
-  }),
-}
-
-const state = State.SQLite.makeState({ tables, materializers: {} })
-
-export const schema = makeSchema({ events, state })
-
-export { tables }
-```
-
-</TabItem>
-</Tabs>
-
-## Further notes
-
-### Cloudflare Workers
-
-- The `@livestore/adapter-node` adapter doesn't yet work with Cloudflare Workers but you can follow [this issue](https://github.com/livestorejs/livestore/issues/266) for a Cloudflare adapter to enable this use case.
-- Having a `@livestore/adapter-cf-worker` adapter could enable serverless server-side client scenarios.

package/docs/patterns/side-effects/index.md

@@ -1,11 +0,0 @@
-# Side effect
-
-TODO: Document how to safely run side-effects as response to LiveStore events.
-
-Notes for writing those docs:
-- Scenarios:
-  - Run side-effect in each client session
-  - Run side-effect only once per client (i.e. use a lock between client sessions)
-  - Run side-effect only once globally (will require some kind of global transaction)
-- How to deal with rollbacks/rebases
-- Allow for filtering events based on whether they have been confirmed by the sync backend or include unconfirmed events

package/docs/patterns/state-machines/index.md

@@ -1,11 +0,0 @@
-# State machines
-
-LiveStore can be used to implement state machines or together with existing state machine libraries (e.g. [XState](https://stately.ai/docs/xstate)).
-
-The basic idea is to listen query results and emit events when the query results change. The state machine side effects can then further commit new mutations to LiveStore.
-
-## Example
-
-```ts
-// TODO (contribution welcome)
-```