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

package/docs/building-with-livestore/syncing/index.md

@@ -1,136 +0,0 @@
-# Syncing
-
-## How it works
-
-LiveStore is based on [the idea of event-sourcing](/understanding-livestore/event-sourcing) which means it syncs events across clients (via a central sync backend) and then materializes the events in the local SQLite database. This means LiveStore isn't syncing the SQLite database itself directly but only the events that are used to materialize the database making sure it's kept in sync across clients.
-
-The syncing mechanism is similar to how Git works in that regard that it's based on a "push/pull" model. Upstream events always need to be pulled before a client can push its own events to preserve a [global total order of events](https://medium.com/baseds/ordering-distributed-events-29c1dd9d1eff). Local pending events which haven't been pushed yet need to be rebased on top of the latest upstream events before they can be pushed.
-
-<SyncingDiagram />
-
-## Events
-
-A LiveStore event consists of the following data:
-- `seqNum`: event sequence number
-- `parentSeqNum`: parent event sequence number
-- `name`: event name (refers to a event definition in the schema)
-- `args`: event arguments (encoded using the event's schema definition, usually JSON)
-
-### Event sequence numbers
-
-- Event sequence numbers: monotonically increasing integers
-  - client event sequence number to sync across client sessions (never exposed to the sync backend)
-
-### Sync heads
-
-- The latest event in a eventlog is referred to as the "head" (similar to how Git refers to the latest commit as the "head").
-- Given that LiveStore does hierarchical syncing between the client session, the client leader and the sync backend, there are three heads (i.e. the client session head, the client leader head, and the sync backend head).
-
-## Sync backend
-
-The sync backend acts as the global authority and determines the total order of events ("causality"). It's responsible for storing and querying events and for notifying clients when new events are available.
-
-### Requirements for sync backend
-
-- Needs to provide an efficient way to query an ordered list of events given a starting event ID (often referred to as cursor).
-- Ideally provides a "reactivity" mechanism to notify clients when new events are available (e.g. via WebSocket, HTTP long-polling, etc).
-  - Alternatively, the client can periodically query for new events which is less efficient.
-
-## Clients
-
-- Each client initially chooses a random `clientId` as its globally unique ID
-  - LiveStore uses a 6-char nanoid
-	- In the unlikely event of a collision which is detected by the sync backend the first time a client tries to push, the client chooses a new random `clientId`, patches the local events with the new `clientId`, and tries again.
-
-### Client sessions
-
-- Each client has at least one client session
-- Client sessions within the same client share local data
-- In web adapters: multiple tabs/windows can be different sessions within the same client
-- Sessions are identified by a `sessionId` which can persist (e.g., across tab reloads in web)
-- For adapters which support multiple client sessions (e.g. web), LiveStore also supports local syncing across client sessions (e.g. across browser tabs or worker threads)
-- Client session events are not synced to the sync backend
-
-## Auth (authentication & authorization)
-
-- TODO
-  - Provide basic example
-  - Encryption
-
-## Advanced
-
-### Sequence diagrams
-
-#### Pulling events (without unpushed events)
-
-```d2
-...@../../../../src/content/base.d2
-
-shape: sequence_diagram
-
-Client: {
-  label: "Client"
-}
-
-SyncBackend: {
-  label: "Sync Backend"
-}
-
-Client -> SyncBackend: "`pull` request\n(head_cursor)"
-SyncBackend -> SyncBackend: "Get new events\n(since head_cursor)"
-SyncBackend -> Client: "New events"
-Client -> Client: "Client is in sync"
-```
-
-#### Pushing events
-
-```d2
-...@../../../../src/content/base.d2
-
-shape: sequence_diagram
-
-Client: {
-  label: "Client"
-}
-
-SyncBackend: {
-  label: "Sync Backend"
-}
-
-Client -> Client: "Commit events"
-Client -> SyncBackend: "`push` request\n(new_local_events)"
-SyncBackend -> SyncBackend: "Validate & persist"
-SyncBackend -> Client: "Push success"
-Client -> Client: "Client is in sync"
-```
-
-### Rebasing
-
-### Merge conflicts
-
-- Merge conflict handling isn't implemented yet (see [this issue](https://github.com/livestorejs/livestore/issues/253)).
-- Merge conflict detection and resolution will be based on the upcoming [facts system functionality](https://github.com/livestorejs/livestore/issues/254).
-
-### Compaction
-
-- Compaction isn't implemented yet (see [this issue](https://github.com/livestorejs/livestore/issues/136))
-- Compaction will be based on the upcoming [facts system functionality](https://github.com/livestorejs/livestore/issues/254).
-
-### Partitioning
-
-- Currently LiveStore assumes a 1:1 mapping between an eventlog and a SQLite database.
-- In the future, LiveStore aims to support multiple eventlogs (see [this issue](https://github.com/livestorejs/livestore/issues/255)).
-
-## Design decisions / trade-offs
-
-- Require a central sync backend to enforce a global total order of events.
-  - This means LiveStore can't be used in a fully decentralized/P2P manner.
-- Do rebasing on the client side (instead of on the sync backend). This allows the user to have more control over the rebase process.
-
-## Notes
-
-- Rich text data is best handled via CRDTs (see [#263](https://github.com/livestorejs/livestore/issues/263))
-
-## Further reading
-
-- Distributed Systems lecture series by Martin Kleppmann: [YouTube playlist](https://www.youtube.com/playlist?list=PLeKd45zvjcDFUEv_ohr_HdUFe97RItdiB) / [lecture notes](https://www.cl.cam.ac.uk/teaching/2122/ConcDisSys/dist-sys-notes.pdf)

package/docs/building-with-livestore/tools/cli/index.md

@@ -1,177 +0,0 @@
-# LiveStore CLI
-
-The LiveStore CLI provides tools for creating new projects and integrating with AI assistants through MCP (Model Context Protocol).
-
-:::caution[Experimental - Not Production Ready]
-The LiveStore CLI is an experimental preview and not ready for production use. APIs, commands, and functionality may change significantly. Use for development and evaluation purposes only.
-:::
-
-## Installation
-
-You can use the LiveStore CLI in several ways:
-
-```bash
-# Recommended: Use bunx (no installation needed)
-bunx @livestore/cli --help
-
-# Alternative options:
-npm install -g @livestore/cli        # Global install
-npm install -D @livestore/cli        # Project install
-npx @livestore/cli --help            # Use with npx
-```
-
-## Commands
-
-### `livestore new-project`
-Create a new LiveStore project from available examples.
-
-```bash
-# Interactive selection
-livestore new-project
-
-# Specify example and path
-livestore new-project --example web-todomvc my-project
-
-# Use specific branch
-livestore new-project --branch dev
-```
-
-### `livestore mcp`
-MCP server tools for AI assistant integration. See [MCP Integration](/building-with-livestore/tools/mcp) for details.
-
-```bash
-# Start MCP server
-livestore mcp
-
-# Available subcommands
-livestore mcp coach    # AI coaching assistant (requires API key env var)
-livestore mcp tools    # Development tools server
-
-# Coach command requires API key - check implementation for specific variable name
-# Example: OPENAI_API_KEY=your_key livestore mcp coach
-```
-
-### `livestore sync`
-
-Import and export events from the sync backend. Useful for backup, migration, and debugging.
-
-#### Export
-
-Export all events from the sync backend to a JSON file:
-
-```bash
-livestore sync export \
-  --config livestore-cli.config.ts \
-  --store-id my-store \
-  events.json
-```
-
-**Example output:**
-
-```
-Exporting events from LiveStore...
-   Config: livestore-cli.config.ts
-   Store ID: my-store
-   Output: events.json
-
-Connecting to sync backend...
-✓ Connected to sync backend: @livestore/cf-sync
-Pulling events from sync backend...
-Pulled 127 events
-Exported 127 events to /path/to/events.json
-```
-
-**Options:**
-- `--config, -c` (required) - Path to a config module that exports `schema` and `syncBackend`
-- `--store-id, -i` (required) - Store identifier
-- `--client-id` - Client identifier for the sync connection (default: `cli-export`)
-- Large exports load data in memory; for very large stores run this on a machine with sufficient RAM.
-
-#### Import
-
-Import events from a JSON file to the sync backend:
-
-```bash
-livestore sync import \
-  --config livestore-cli.config.ts \
-  --store-id my-store \
-  events.json
-```
-
-**Example output:**
-
-```
-Importing events to LiveStore...
-   Config: livestore-cli.config.ts
-   Store ID: my-store
-   Input: events.json
-
-Reading import file...
-Found 127 events in export file
-Checking for existing events...
-Connecting to sync backend...
-✓ Connected to sync backend: @livestore/cf-sync
-Pushing events to sync backend...
-  Pushed 100/127 events
-  Pushed 127/127 events
-Successfully imported 127 events
-```
-
-**Options:**
-- `--config, -c` (required) - Path to a config module that exports `schema` and `syncBackend`
-- `--store-id, -i` (required) - Store identifier
-- `--client-id` - Client identifier for the sync connection (default: `cli-import`)
-- `--force, -f` - Force import even if store ID in the file doesn't match
-- `--dry-run` - Validate the import file without actually importing
-- Large imports are memory-intensive because the JSON is loaded fully before validation/push.
-
-**Note:** The sync backend must be empty when importing. The import will fail if events already exist.
-
-### Config file
-
-Both MCP and sync commands require a config file (conventionally named `livestore-cli.config.ts`) that exports:
-
-## `reference/cli/config.ts`
-
-```ts filename="reference/cli/config.ts"
-
-// Re-export your app's schema (adjust path to your project)
-export { schema } from './schema.ts'
-
-// Provide a sync backend constructor
-export const syncBackend = makeWsSync({
-  url: process.env.LIVESTORE_SYNC_URL ?? 'ws://localhost:8787',
-})
-
-// Optionally, pass an auth payload (must be JSON-serializable)
-export const syncPayload = {
-  authToken: process.env.LIVESTORE_SYNC_AUTH_TOKEN,
-}
-```
-
-### `reference/cli/schema.ts`
-
-```ts filename="reference/cli/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 })
-```
-
-## Global options
-
-- `--verbose` - Enable verbose logging
-- `--help` - Show command help

package/docs/building-with-livestore/tools/mcp/index.md

@@ -1,187 +0,0 @@
-# MCP integration
-
-LiveStore includes MCP (Model Context Protocol) integration that allows AI assistants like Claude to access LiveStore documentation, examples, and development tools.
-
-:::caution[Experimental]
-The MCP integration is experimental and under active development. Features may change.
-:::
-
-For installation and general CLI usage, see the [LiveStore CLI](/building-with-livestore/tools/cli) documentation.
-
-## What is MCP?
-
-MCP (Model Context Protocol) is a standard for providing AI assistants with access to external resources and tools. LiveStore's MCP server gives AI assistants access to:
-
-- LiveStore documentation and guides
-- Schema examples for common app types
-- Development tools and utilities
-
-## Usage
-
-Start the MCP server:
-
-```bash
-bunx @livestore/cli mcp
-```
-
-## Available commands
-
-### `bunx @livestore/cli mcp coach`
-Starts an AI coaching assistant with access to LiveStore documentation and best practices.
-
-### `bunx @livestore/cli mcp tools`
-Provides development tools and utilities for working with LiveStore projects.
-
-### LiveStore Runtime Tools
-
-- `livestore_instance_connect`
-  - Connects a single in-process LiveStore instance by dynamically importing a module that exports `schema` and a `syncBackend` factory (and optionally `syncPayload`).
-  - Notes:
-    - Only one instance can be active at a time; connecting again shuts down and replaces the previous instance.
-    - Reconnecting creates a fresh, in-memory client database. The visible state is populated by your backend's initial sync. Until sync completes, queries may return empty or partial results.
-  - Module contract (generic example):
-
-## `reference/mcp/module-contract.ts`
-
-```ts filename="reference/mcp/module-contract.ts"
-
-export { schema } from './schema.ts'
-
-export const syncBackend = makeWsSync({ url: process.env.LIVESTORE_SYNC_URL ?? 'ws://localhost:8787' })
-
-export const syncPayload = { authToken: process.env.LIVESTORE_SYNC_AUTH_TOKEN ?? 'insecure-token-change-me' }
-```
-
-### `reference/mcp/schema.ts`
-
-```ts filename="reference/mcp/schema.ts"
-
-const events = {
-  entityCreated: Events.synced({
-    name: 'v1.EntityCreated',
-    schema: Schema.Struct({
-      id: Schema.String,
-      title: Schema.String,
-      createdAt: Schema.DateFromString,
-    }),
-  }),
-}
-
-const tables = {
-  entities: State.SQLite.table({
-    name: 'entities',
-    columns: {
-      id: State.SQLite.text({ primaryKey: true }),
-      title: State.SQLite.text({ default: '' }),
-      createdAt: State.SQLite.text({ default: '' }),
-    },
-  }),
-}
-
-const materializers = State.SQLite.materializers(events, {
-  'v1.EntityCreated': ({ id, title, createdAt }) =>
-    tables.entities.insert({ id, title, createdAt: createdAt.toISOString() }),
-})
-
-const state = State.SQLite.makeState({ tables, materializers })
-
-export const schema = makeSchema({ events, state })
-```
-
-- Params example: `{ "configPath": "livestore-cli.config.ts", "storeId": "<store-id>" }`
-  - Returns example:
-    `{ "storeId": "<store-id>", "clientId": "client-123", "sessionId": "session-abc", "schemaInfo": { "tableNames": ["..."], "eventNames": ["..."] } }`
-
-- `livestore_instance_query`
-  - Executes raw SQL against the client database (read-only).
-  - Notes:
-    - SQLite dialect; use valid SQLite syntax.
-    - `bindValues` must be an array (positional `?`) or a record (named `$key`). Do not pass stringified JSON.
-  - Params example (positional): `{ "sql": "SELECT * FROM my_table WHERE userId = ?", "bindValues": ["u1"] }`
-  - Params example (named): `{ "sql": "SELECT * FROM my_table WHERE userId = $userId", "bindValues": { "userId": "u1" } }`
-  - Returns example: `{ "rows": [{ "col": "value" }], "rowCount": 1 }`
-
-- `livestore_instance_commit_events`
-  - Commits one or more events defined by your connected schema.
-  - Notes:
-    - Use the canonical event name declared in your schema (e.g., `v1.EntityCreated`).
-    - `args` must be a non-stringified JSON object matching the event schema. Date fields typically accept ISO 8601 strings.
-  - Params example: `{ "events": [{ "name": "v1.EntityCreated", "args": { "id": "e1", "title": "Hello", "createdAt": "2024-01-01T00:00:00.000Z" } }] }`
-  - Returns example: `{ "committed": 1 }`
-
-- `livestore_instance_status`
-  - Reports instance/runtime info.
-  - Returns example (connected): `{ "_tag": "connected", "storeId": "<store-id>", "clientId": "client-123", "sessionId": "session-abc", "tableCounts": { "my_table": 12 } }`
-  - Returns example (not connected): `{ "_tag": "disconnected" }`
-
-- `livestore_instance_disconnect`
-  - Disconnects the current LiveStore instance and releases resources.
-  - Returns: `{ "_tag": "disconnected" }`
-
-### Sync export/import tools
-
-These tools connect directly to the sync backend (without creating a full LiveStore instance) to export or import events. Useful for backup, migration, and debugging.
-
-- `livestore_sync_export`
-  - Exports all events from a sync backend to JSON data.
-  - Notes:
-    - Connects directly to the sync backend and pulls all events.
-    - Returns the export data as a JSON object that can be saved or passed to import.
-  - Params example: `{ "configPath": "livestore-cli.config.ts", "storeId": "my-store" }`
-  - Returns example: `{ "storeId": "my-store", "eventCount": 127, "exportedAt": "2024-01-15T10:30:00.000Z", "data": { "version": 1, "storeId": "my-store", "events": [...] } }`
-
-- `livestore_sync_import`
-  - Imports events from export data to a sync backend.
-  - Notes:
-    - The sync backend must be empty before importing.
-    - Use `force: true` to import even if the store ID in the data doesn't match.
-    - Use `dryRun: true` to validate the import without actually importing.
-  - Params example: `{ "configPath": "livestore-cli.config.ts", "storeId": "my-store", "data": { "version": 1, "storeId": "my-store", "events": [...] } }`
-  - Params with options: `{ "configPath": "...", "storeId": "...", "data": {...}, "force": true, "dryRun": true }`
-  - Returns example: `{ "storeId": "my-store", "eventCount": 127, "dryRun": false }`
-
-## Local Cloudflare sync (dev)
-
-Run a local Cloudflare sync backend:
-
-1. Start the sync worker (wrangler):
-   - `cd tests/integration/src/tests/adapter-cloudflare/fixtures`
-   - `wrangler dev`
-   - You should see an info page at `http://localhost:8787/`.
-
-2. Start the MCP server in another terminal:
-   - `bunx @livestore/cli mcp server`
-
-3. From your MCP client (e.g., Claude Desktop), call tools:
-   - Use your own config file path and storeId. The repo also provides an example: `examples/cf-chat/livestore-cli.config.ts`.
-   - Connect: `livestore_instance_connect` with `{ "configPath": "livestore-cli.config.ts", "storeId": "<store-id>" }`
-   - Commit: `livestore_instance_commit_events` with `[ { "name": "v1.EntityCreated", "args": { "id": "e1", "title": "Hello", "createdAt": "2024-01-01T00:00:00.000Z" } } ]`
-   - Query: `livestore_instance_query` with `{ "sql": "SELECT * FROM my_table ORDER BY createdAt DESC LIMIT 5" }`
-   - Status: `livestore_instance_status`
-   - Disconnect: `livestore_instance_disconnect`
-
-## Adding to Claude
-
-To use with Claude Desktop, add the MCP server to your Claude configuration:
-
-```json
-{
-  "mcpServers": {
-    "livestore": {
-      "command": "bunx",
-      "args": ["@livestore/cli", "mcp"]
-    }
-  }
-}
-```
-
-## Available resources
-
-The MCP server provides access to:
-
-- **Documentation**: Overview, features, getting started guides
-- **Architecture**: Technical design and principles  
-- **Schema Examples**: Pre-built schemas for todo, blog, e-commerce, and social apps
-- **Development Tools**: Project scaffolding and utilities
-
-This enables AI assistants to provide context-aware help with LiveStore development.

package/docs/examples/cloudflare-adapter/index.md

@@ -1,44 +0,0 @@
-# Cloudflare Durable Objects examples
-
-# Cloudflare Durable Objects Examples
-
-Examples using `@livestore/adapter-cloudflare` for Cloudflare Workers and Durable Objects.
-
-<CardGrid>
-{cloudflareExamples.map((example) => {
-  const { url, label } = getExampleDemoLinks(example);
-
-  return (
-    <Card title={example.title} key={example.title}>
-    {example.image ? (
-      <Image src={example.image.url} width={example.image.width} height={example.image.height} alt={`${example.title} application interface`} />
-    ) : (
-      <div style="background: linear-gradient(135deg, #1f2937 0%, #374151 100%); height: 200px; display: flex; align-items: center; justify-content: center; color: #9ca3af; font-size: 14px; border-radius: 8px;">
-        Screenshot coming soon
-      </div>
-    )}
-    <p>{example.description}</p>
-    <p><strong>Technologies:</strong> {example.technologies.join(' • ')}</p>
-    {example.syncProvider && (
-      <p><strong>Sync Provider:</strong> {example.syncProvider}</p>
-    )}
-    <div style="margin-top: auto; padding-top: 1rem;">
-      {url && (
-        <p style="margin: 0 0 0.5rem 0;"><a href={url} target="_blank" rel="noopener noreferrer">{label}</a></p>
-      )}
-      <p style="margin: 0;"><a href={example.sourceUrl} target="_blank" rel="noopener noreferrer">View Source →</a></p>
-    </div>
-    </Card>
-  );
-})}
-</CardGrid>
-
-## Cloudflare Adapter
-
-- Runs LiveStore inside Cloudflare Durable Objects
-- Uses Durable Object Storage API (not traditional databases)
-- SQLite WASM with Cloudflare-specific VFS
-- No WebSocket support - uses Durable Objects' distributed consistency
-
----
-<a href={`https://github.com/livestorejs/livestore/tree/${getBranchName()}/examples`}>View all examples on GitHub →</a>

package/docs/examples/expo-adapter/index.md

@@ -1,44 +0,0 @@
-# Expo adapter examples
-
-# Expo Adapter Examples
-
-Examples using `@livestore/adapter-expo` for React Native mobile applications.
-
-<CardGrid>
-{expoExamples.map((example) => {
-  const { url, label } = getExampleDemoLinks(example);
-
-  return (
-    <Card title={example.title} key={example.title}>
-    {example.image ? (
-      <Image src={example.image.url} width={example.image.width} height={example.image.height} alt={`${example.title} application interface`} />
-    ) : (
-      <div style="background: linear-gradient(135deg, #1f2937 0%, #374151 100%); height: 200px; display: flex; align-items: center; justify-content: center; color: #9ca3af; font-size: 14px; border-radius: 8px;">
-        Screenshot coming soon
-      </div>
-    )}
-    <p>{example.description}</p>
-    <p><strong>Technologies:</strong> {example.technologies.join(' • ')}</p>
-    {example.syncProvider && (
-      <p><strong>Sync Provider:</strong> {example.syncProvider}</p>
-    )}
-    <div style="margin-top: auto; padding-top: 1rem;">
-      {url && (
-        <p style="margin: 0 0 0.5rem 0;"><a href={url} target="_blank" rel="noopener noreferrer">{label}</a></p>
-      )}
-      <p style="margin: 0;"><a href={example.sourceUrl} target="_blank" rel="noopener noreferrer">View Source →</a></p>
-    </div>
-    </Card>
-  );
-})}
-</CardGrid>
-
-## Expo Adapter
-
-- Uses native Expo SQLite stored in device's SQLite directory
-- Requires New Architecture (Fabric) - incompatible with old architecture
-- Single-threaded operation in main thread
-- WebSocket connections for sync via React Native dev server
-
----
-<a href={`https://github.com/livestorejs/livestore/tree/${getBranchName()}/examples`}>View all examples on GitHub →</a>

package/docs/examples/index.md

@@ -1,55 +0,0 @@
-# Examples
-
-# Example Applications
-
-Discover how to build local-first applications with LiveStore through our comprehensive collection of example apps. Each example demonstrates different features, patterns, and platform integrations to help you get started quickly.
-
-## Browse by platform adapter
-
-LiveStore supports multiple platform adapters, each optimized for different environments. Choose the adapter that matches your target platform:
-
-<CardGrid>
-  <LinkCard 
-    title="Web Adapter" 
-    href="/examples/web-adapter/"
-    description={`Browser-based applications with SQLite WASM, Web Workers, and framework integrations. ${webExamples.length} examples • React, SolidJS, Svelte, Web Components`}
-  />
-
-  <LinkCard 
-    title="Node Adapter" 
-    href="/examples/node-adapter/"
-    description={`Server-side applications, CLI tools, and backend services with native SQLite performance. ${nodeExamples.length} examples • Effect, CLI applications`}
-  />
-
-  <LinkCard 
-    title="Expo Adapter" 
-    href="/examples/expo-adapter/"
-    description={`React Native mobile applications with offline-first architecture and cross-platform sync. ${expoExamples.length} examples • iOS, Android, React Native`}
-  />
-
-  <LinkCard 
-    title="Cloudflare Durable Objects" 
-    href="/examples/cloudflare-adapter/"
-    description={`Edge computing with Durable Objects, global distribution, and serverless scaling. ${cloudflareExamples.length} examples • Workers, Durable Objects, Edge`}
-  />
-</CardGrid>
-
-## Getting started
-
-1. **Choose your platform** from the adapter categories above
-2. **Browse examples** that match your use case and framework preference  
-3. **Clone and run** the examples locally to see LiveStore in action
-4. **Study the source code** to understand patterns and best practices
-
-## Multi-adapter examples
-
-Some examples demonstrate **cross-platform synchronization** by using multiple adapters:
-- **CF Chat** uses both Web and Cloudflare adapters for hybrid client-server architecture
-- **Sync-enabled examples** show how to connect different platforms seamlessly
-
-## About LiveStore
-
-LiveStore is a local-first data layer that runs everywhere - from browsers to mobile apps to edge computing. Each adapter provides platform-optimized features while maintaining a consistent API across all environments.
-
----
-<a href={`https://github.com/livestorejs/livestore/tree/${getBranchName()}/examples`}>View all examples on GitHub →</a>