This is the full developer documentation for LiveStore. # Start of LiveStore documentation # [Docs](https://dev.docs.livestore.dev//) ## Overview import { CardGrid, LinkCard } from '@astrojs/starlight/components'; import { LIVESTORE_WA_SQLITE_VERSION } from '../../../../CONSTANTS.ts' import { officeHours } from '../../../data.js' import { liveStoreVersion } from '@livestore/common' import NpmLink from '../../components/NpmLink.astro' ## State of the documentation Please note that the documentation is still work in progress with many parts missing and often only containing notes/bullet points. ### Docs for LLMs We support the [llms.txt](https://llmstxt.org/) convention for making documentation available to large language models and the applications that make use of them. Currently, we have the following root-level files: - [/llms.txt](/llms.txt) — a listing of the available files - [/llms-full.txt](/llms-full.txt) — complete documentation for LiveStore ### NPM packages - Main package: - Framework integrations: - React: - Solid: - Platform adapters: - Web: - Expo: - Node: - Sync provider: - Cloudflare: - Electric: - Devtools: - Vite: - Expo: - SQLite WASM: - Note this package has a separate version from the rest of LiveStore - Internal packages: - - - # [Contributing](https://dev.docs.livestore.dev/contributing/contributing/) ## Overview ## Before contributing First of all, thank you for your interest in contributing to LiveStore! Building LiveStore has been an incredible amount of work, so everyone interested in contributing is very much appreciated. 🧡 Please note that LiveStore is still in active development with many things yet subject to change (e.g. APIs, examples, docs, etc). Before you start contributing, please check with the maintainers if the changes you'd like to make are likely to be accepted. Please get in touch via the `#contrib` channel on [Discord](https://discord.gg/RbMcjUAPd7). ## Areas for contribution There are many ways to contribute to LiveStore. ### Help wanted for ... - You can look at ["help wanted" issues](https://github.com/livestorejs/livestore/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) on GitHub for ideas. - [SQLite WASM build](https://github.com/livestorejs/wa-sqlite) maintainer (e.g. keeping it up to date with upstream SQLite and wa-sqlite versions) - Examples maintainer (e.g. keeping dependencies & best practices up to date) - Solid integration maintainer (e.g. keeping it up to date with upstream Solid versions) ### In scope and encouraged - Documentation improvements - Improving examples - Test cases - Bug fixes - Benchmarking ### Potentially in scope - New features - Larger architectural changes in the core library - Adding new examples - Adding new integrations (e.g. for technologies such as Svelte, Vue, ...) - Monorepo setup changes - Changes to the docs site/setup ### Out of scope (for now) - Changes to the landing page - Changes to the devtools - Rewriting the core library in a different language ### Open research questions - Safer event schema evolution - Incremental view maintenance for complex SQLite database views Please get in touch if you'd like to discuss any of these topics! ## Guiding principles {#guiding-principles} - Keep it as simple as possible - Reduce surface area - Make the right thing easy - Document the "why" # [Docs](https://dev.docs.livestore.dev/contributing/docs/) ## Overview Please follow LiveStore's [guiding principles](/contributing/contributing#guiding-principles) when writing docs. ## Writing style This project broadly tries to follow the [Prisma docs style guide](https://www.prisma.io/docs/about/style-guide/writing-style). ## Reusing code When including code snippets, please try to `import` the code from the source in order to avoid duplication. # [Monorepo](https://dev.docs.livestore.dev/contributing/monorepo/) ## Overview import { REACT_VERSION, EFFECT_VERSION } from '../../../../../CONSTANTS' ## Prerequisites ### Personal experience Depending on the kind of contribution you're interested in, the following experience is recommended: - Deep experience with TypeScript (incl. type-level programming) - Experience with TypeScript monorepo setups - Experience with distributed systems - Experience with [Effect](https://effect.website) (or willingness to learn) ### Recommended tooling: Use Nix + direnv for a consistent development setup To make development as easy and consistent across systems and platforms, this project uses [Nix](https://zero-to-nix.com/) to manage "system dependencies" such as Node.js, Bun etc. You can either use [Direnv](https://direnv.net) setup (recommended) to automatically load the Nix env or manually use the Nix env (e.g. via `nix develop --command pnpm install`). ### Manual setup You'll need to have a recent version the following tools installed: - Node.js - Bun - pnpm ## Initial setup ```bash git clone git@github.com:livestorejs/livestore.git cd livestore # Load environment variables (including Nix dependencies) direnv allow # Install dependencies pnpm install # Build the project pnpm build ``` ## General notes - TypeScript - LiveStore tries to follow the strictest TypeScript rules possible to ensure type safety and avoid subtle bugs. - LiveStore also makes heavy use of [TypeScript project references](https://www.typescriptlang.org/docs/handbook/project-references.html). - Package management - This project uses [pnpm](https://pnpm.io/) to manage the workspace. - LiveStore is primarily developed in VSCode/Cursor. - Testing - LiveStore uses Vitest for most tests and Playwright for browser tests. ### Notable used tools / technologies - [TypeScript](https://www.typescriptlang.org/) - [Effect](https://effect.website) - [pnpm](https://pnpm.io/) - [Bun](https://bun.sh/) - [Vitest](https://vitest.dev/) - [Playwright](https://playwright.dev/) - [OpenTelemetry](https://opentelemetry.io/) - [Nix](https://zero-to-nix.com/) - [Direnv](https://direnv.net/) ### Environment variables The `.envrc` file contains all necessary environment variables for the project. You can create a `.envrc.local` file to override or add variables for your local setup. You'll need to run `direnv allow` to load the environment variables. ### VSCode tasks - This project is primarily developed in VSCode and makes use of [tasks](https://code.visualstudio.com/docs/editor/tasks) to run commands. - Common tasks are: - `dev:ts` to run the TypeScript compiler in watch mode for the entire monorepo - `pnpm:install` to install all dependencies (e.g. when changing a `package.json`) ## Examples - Once you've set up the monorepo locally, you'll notice both the `src` and `standalone` directories in `/examples`. - The `/examples/standalone` directory is meant as a starting point for app developers evaluating LiveStore and looking for a ready-to-run example app. - The `/examples/src` directory is meant for LiveStore maintainers and to run as part of the LiveStore monorepo. Compared to `/examples/standalone` it makes use of local linking features such a `workspace:*`, TypeScript `references` etc. - Both directories are kept in sync via `/examples/patches` and `/scripts/generate-examples.ts`. Usually it's recommended to work in `/examples/src` and generate the `/examples/standalone` version via `mono examples sync --direction src-to-standalone`. #### Making changes to examples 1. Make your desired changes in `/examples/src`. (You might also need to update some of the patches in `/examples/patches`.) 2. Run `mono examples sync --direction src-to-standalone` to generate the `/examples/standalone` version 3. Check whether the changes in `/examples/standalone` are what you expected. 4. Commit your changes in both `/examples/src` and `/examples/standalone` (and possibly `/examples/patches`). Note on GitHub, changes to `examples/standalone` are hidden by default. ### OpenTelemetry setup As a local OpenTelemetry setup, we recommend the [docker-otel-lgtm](https://github.com/grafana/docker-otel-lgtm) setup. Add the following to your `.envrc.local` file: ```bash export VITE_GRAFANA_ENDPOINT="http://localhost:30003" export GRAFANA_ENDPOINT="http://localhost:30003" export OTEL_EXPORTER_OTLP_ENDPOINT="http://localhost:4318" export VITE_OTEL_EXPORTER_OTLP_ENDPOINT="http://localhost:4318" ``` ### TypeScript - Each package has its own `tsconfig.json` file which extends the root `tsconfig.base.json`. - This project makes heavy use of TypeScript project references. ### Package management - This project uses [pnpm](https://pnpm.io/) to manage the workspace. - We're using the `workspace:*` protocol to link packages together. - We should try to keep dependencies to an absolute minimum and only add them if we absolutely need them. - We also need to manually add peer dependencies for each package. - We should try to avoid duplicate dependencies across the monorepo as much as possible as duplicate dependencies can lead to a lot of issues and pain. - We're also using the `resolutions` field in the root `package.json` to force some packages to be the same across the monorepo (ideally not needed but for some packages it's necessary currently). - We're using [syncpack](https://github.com/JamieMason/syncpack) to help maintain consistent dependency versions across the monorepo. - See `syncpack.config.mjs` for the configuration. - Common commands: - `bunx syncpack format` to format the `package.json` files - `bunx syncpack lint` to check all version ranges - `bunx syncpack fix-mismatches` to adjust versions across `package.json` files (check before with `lint`) - `bunx syncpack update` to update packages across the monorepo to the latest versions ### Notes on external dependencies LiveStore tries to use as few external dependencies as possible. Given LiveStore is built on top of Effect, which can be considered a standard library for TypeScript, it should handle most use cases. #### Notes on some packages The following packages need to be updated with extra care: - `react`/`react-dom` as we need to move in lockstep with Expo / React Native (currently pinned to {REACT_VERSION}) - `effect` (currently pinned to {EFFECT_VERSION}) #### Effect - LiveStore makes heavy use of the [Effect](https://effect.website) library and ecosystem throughout the implementation of the various packages. - Effect is not imposed on the app developers using LiveStore but where it makes sense, LiveStore is also exposing a Effect-based API (e.g. `createStore`). #### Updating dependencies - Either update the versions manually in each `package.json` file or use `bunx syncpack update`. ### Notes on monorepo structure - The `@livestore/utils` package re-exports many common modules/functions (e.g. from `effect`) in order to - Reduce the number of direct dependencies for other packages - Allows for convenient extension of modules (e.g. adding methods to `Effect.___`, `Schema.___`, ...) ## Docs The LiveStore docs are built with [Astro Starlight](https://starlight.astro.build/). ## Related external repos - [Fork of wa-sqlite](https://github.com/livestorejs/wa-sqlite) and its [Nix build setup](https://github.com/livestorejs/wa-sqlite-build-env?tab=readme-ov-file). - The source code of the devtools is currently not part of this monorepo but in a separate private repo. # [AI agent](https://dev.docs.livestore.dev/data-modeling/ai-agent/) ## Overview LiveStore is a great fit for building AI agents. TODO: actually write this section # [Complex UI state](https://dev.docs.livestore.dev/data-modeling/complex-ui-state/) ## Overview LiveStore is a great fit for building apps with complex UI state. TODO: actually write this section # [Data Modeling](https://dev.docs.livestore.dev/data-modeling//) ## Overview ## Core idea - Data modeling is probably the most important part of any app and needs to be done carefully. - The core idea is to model the read and write model separately. - Depending on the use case, you might also want to split up the read/write model into separate "containers" (e.g. for data-sharing/scalability/access control reasons). - There is no transactional consistency between containers. - Caveat: Event sourcing is not ideal for all use cases - some apps might be better off with another approach (e.g. use CRDTs for rich text editing). ## Considerations for data modeling - How much data do you expect to have and what is the shape of the data? - Some kind of data needs special handling (e.g. blobs or rich text) - Access patterns (performance, ...) - Access control - Data integrity / consistency - Sharing / collaboration - Regulatory requirements (e.g. GDPR, audit logs, ...) ## TODO - TODO: actually write this section - questions to answer - When to split things into separate containers? - How do migrations work? - Read model migrations - Write model migrations - How to create new write models based on existing ones - Example: An app has multiple workspaces and you now want to introduce the concept of "projects" inside a workspace. You might want to pre-populate a "default workspace project" for each workspace. # [Todo app with shared workspaces](https://dev.docs.livestore.dev/data-modeling/todo-workspaces/) ## Overview import { Code, Tabs, TabItem } from '@astrojs/starlight/components'; Let's consider a fairly common application scenario: An app (in this case a todo app) with shared workspaces. For the sake of this guide, we'll keep things simple but you should be able to nicely extend this to a more complex app. ## Requirements - There are multiple independent todo workspaces - Each workspace is initially created by a single user - Users can join the workspace by knowing the workspace id and get read and write access - For simplicity, the user identity is chosen when the app initially starts (i.e. a username) but in a real app this would be handled by a proper auth setup ## Data model - We are splitting up our data model into two kinds of stores (with respective eventlogs and SQLite databases): The `workspace` store and the `user` store. ### `workspace` store (one per workspace) For the `workspace` store we have the following events: - `workspaceCreated` - `todoAdded` - `todoCompleted` - `todoDeleted` - `userJoined` And the following state model: - `workspace` table (with a single row for the workspace itself) - `todo` table (with one row per todo item) - `member` table (with one row per user who has joined the workspace) ### `user` store (one per user) For the `user` store we have the following events: - `workspaceCreated` - `workspaceJoined` And the following state model: - `user` table (with a single row for the user itself) Note that the `workspaceCreated` event is used both in the `workspace` and the `user` store. This is because each eventlog should be "self-sufficient" and not rely on other eventlogs to be present to fulfill its purpose. ![](https://share.cleanshot.com/yCbKjvRP+) ## Schema tables.userList.insert({ workspaceId }), workspaceJoined: ({ workspaceId }) => tables.userList.insert({ workspaceId }), }) const state = State.SQLite.makeState({ tables, materializers }) export const schema = makeSchema({ events, state }) `} /> [ tables.workspace.insert({ workspaceId, name, createdByUsername }), // Add the creator as the first member tables.member.insert({ username: createdByUsername }), ], todoAdded: ({ todoId, text }) => tables.todo.insert({ todoId, text }), todoCompleted: ({ todoId }) => tables.todo.update({ completed: true }).where({ todoId }), todoDeleted: ({ todoId, deletedAt }) => tables.todo.update({ deletedAt }).where({ todoId }), userJoined: ({ username }) => tables.member.insert({ username }), }) const state = State.SQLite.makeState({ tables, materializers }) export const schema = makeSchema({ events, state }) `} /> ## Further notes To make this app more production-ready, we might want to do the following: - Use a proper auth setup to enforce a trusted user identity - Introduce a proper user invite process - Introduce access levels (e.g. read-only, read-write) - Introduce end-to-end encryption - If each todo item has a lot of data (e.g. think of a GitHub/Linear issue with lots of details), it might make sense to split up each todo item into its own store. # [Turn-based game](https://dev.docs.livestore.dev/data-modeling/turnbased-game/) ## Overview LiveStore is a great fit for turn-based games. In this guide we'll look at a simple turn-based game and how to model it in LiveStore. General idea: Let server enforce the logic that each player only commits one action per turn. TODO: write rest of guide # [Design Decisions](https://dev.docs.livestore.dev/evaluation/design-decisions/) ## Overview ## Goals - Fast, synchronous, transactional, and reactive state management - Global state is eventually consistent - Persistent storage - Syncing - Convenient schema migrations - Great devtools ## Major Design Decisions - Based on [event-sourcing](/evaluation/event-sourcing) (implying a read/write model separation) - Using SQLite for state management over JavaScript implementations - There are many benefits to using SQLite for state management, including performance, reliability, and ease of use. - Run in-memory SQLite in main-thread to enable synchronous queries - Usually LiveStore is used with a second SQLite database for persistence running in a separate thread (e.g. web worker) - Running SQLite additionally in the main-thread however also means each tab uses extra memory. - The current implementation of LiveStore assumes that the data is small enough to fit in memory. However, SQLite is very efficient so this should work for many use cases and apps. - LiveStore implements a Signals-based reactivity system based on the ideas of Adapton for incremental computation - The goal is to keep LiveStore syncing provider agnostic so you can use the right syncing provider for your use case. ## Implementation decisions - Build most of the library in TypeScript. We might move more parts to Rust in the future. - Embrace and build on top of [Effect](https://effect.website) as a library of powerful primitives, particularly for IO/concurrency heavy parts of the library. ## Original motivation - Frustration with database schema migrations -> event sourcing to separate read and write model (avoid schema migrations for read model) - Applying the "Make the right thing easy" principle to app data management # [Event Sourcing](https://dev.docs.livestore.dev/evaluation/event-sourcing/) ## Overview - Similar to Redux but persisted and synced across devices - Provides a more principled way to handle data instead of relying on mutable state - Core idea: Separate read vs write model - Read model: App database (i.e. SQLite) - Write model: Ordered log of all mutation events - Related topics - Domain driven design - Benefits - Simple mental model - Preserves user intent - Scalable - Flexible - You can easily evolve the read model based on your query patterns as your app requirements change over time - Flexible merge conflicts resolution - Automatic migrations of the read model (i.e. app database) - Write model can also be evolved (e.g. via versioned mutations and optionally mapping old mutations to new ones) - History of all state changes is captured (e.g. for auditing and debugging) - Foundation for syncing - Downsides - Slightly more boilerplate to manually define mutations - Need to be careful so eventlog doesn't grow too much ## LiveStore as an event-sourcing framework While the benefits of event sourcing are compelling, building a robust system from scratch is complex and time-consuming. Developers often encounter pitfalls related to data consistency, schema migrations, and efficient state reconstruction. LiveStore provides an off-the-shelf event sourcing solution designed for ease of use and correctness. It simplifies development by: - Providing clear APIs for defining mutations (events). - Automatically managing the event log persistence and ordering. - Efficiently recomputing the state (e.g. SQLite database) from the eventlog via materializers. - Handling complexities like automatic data migrations and offering strategies for conflict resolution during synchronization. This allows you to leverage the power of event sourcing without needing to implement the underlying infrastructure and tackle common edge cases yourself. ## Further reading - [The Log: What every software engineer should know about real-time data's unifying abstraction](https://engineering.linkedin.com/distributed-systems/log-what-every-software-engineer-should-know-about-real-time-datas-unifying) # [How LiveStore works](https://dev.docs.livestore.dev/evaluation/how-livestore-works/) ## Overview ### TLDR LiveStore uses event sourcing to sync events across clients and materialize state into a local, reactive SQLite database. ![](https://share.cleanshot.com/dTpVv5K1+) ## How LiveStore Works Client-Side On the client, LiveStore provides a reactive SQLite database for application state, which is kept consistent through an underlying event sourcing mechanism. #### Local Reactive SQLite Application state is materialized into a local SQLite database, offering high-performance, offline-capable data access. This SQLite database is reactive: UI components subscribe to data changes and update automatically when the state changes. LiveStore uses in-memory SQLite for sub-millisecond queries and persistent SQLite for durable storage across application sessions. #### Event Sourcing Underpinning the reactive state, LiveStore implements the event sourcing pattern. All data modifications are captured as an immutable, ordered sequence of events. This eventlog serves as the canonical history, enabling reliable state reconstruction and providing inherent auditability, which aids in debugging. The reactive SQLite state is a projection of this eventlog. #### Client-Side Event Flow 1. **Event Committing:** User interactions within the application generate events detailing the specific action (e.g., `TodoCreated`, `TaskCompleted`). 2. **Local Persistence & Materialization:** The committed event is atomically persisted to the local eventlog and immediately materialized as state into the SQLite database. 3. **UI Reactivity:** Changes to the SQLite database trigger the reactivity system, causing subscribed UI components (e.g. React components) to automatically update and reflect the new state. ## How LiveStore Syncing Works LiveStore extends its local event-sourcing model globally by synchronizing events across all clients, typically through a central sync backend. This ensures that the eventlog, serving as the single source of truth, is consistently replicated, leading to an eventually consistent state for all participants. #### Push/Pull Event Synchronization Inspired by Git, LiveStore employs a push/pull model for event synchronization. Clients must first pull the latest events from the sync backend to ensure their local eventlog is up-to-date before they can push their own newly committed local events. This model helps maintain a global total order of events. Local pending events that haven't been pushed are rebased on top of the latest upstream events before being pushed. #### Sync Provider Integration LiveStore supports various sync backend implementations, and it's straightforward for developers to create their own. The sync backend is responsible for storing events, enforcing the total event order, and notifying clients of new events. #### Conflict Resolution When concurrent operations from different clients lead to conflicting events, LiveStore defaults to a "last-write-wins" strategy. However, it also provides the capability for developers to implement custom merge conflict resolution logic tailored to their application's specific needs. #### Overall Syncing Data Flow After a local event is committed and materialized (as per the client-side flow), LiveStore attempts to push this event to the sync backend. Simultaneously, LiveStore is pulling events from the sync backend in the background. Two main scenarios can occur during a push attempt: 1. **Client In Sync:** If the client's local eventlog is already up-to-date with the sync backend (i.e., no new remote events have arrived since the last pull/push), the local event is pushed directly. 2. **Concurrent Incoming Events:** If new remote events have been pulled in the background, or are discovered during the push attempt, the client first processes these incoming remote events. Any local, unpushed events are then rebased on top of these new remote events before being pushed to the sync backend. In both scenarios, once remote events are received (either through background pulling or during a push cycle), they are persisted to the local eventlog, materialized into the local SQLite database, and the UI reacts to the new state, ensuring eventual consistency. ## Platform Adapters LiveStore includes platform adapters to integrate with various environments, such as web browsers, mobile applications (iOS/Android), desktop applications, and Node.js. # [Performance](https://dev.docs.livestore.dev/evaluation/performance/) ## Overview LiveStore is designed with performance in mind. To ensure consistent speed and minimal resource consumption, we maintain a suite of performance tests that run automatically on every commit to `main` and every pull request. These tests help us detect regressions early and identify performance bottlenecks for implementing optimizations. ## Performance tests Our current test suite focuses on two key metrics: **latency** and **memory usage**. We measure these two metrics across various user interaction scenarios on a minimal LiveStore+React test app. We select scenarios that help stress-test LiveStore’s ability to handle common underlying tasks that are part of common user interactions. To learn more about our testing methodology, check out the [README](https://github.com/livestorejs/livestore/blob/main/tests/perf/README.md) of our performance tests. > **Future expansions:** We [plan](https://github.com/livestorejs/livestore/blob/main/tests/perf/README.md#future-improvements) to measure throughput and bundle size, as well as expand the selection of scenarios and dimensions for the tests. ## Latest test results You can view the latest performance test results on our [public dashboard](https://livestore.grafana.net/public-dashboards/4a9a3b7941464bcebbc0fa2cdddc3130). Otherwise, you can view the latest test results by inspecting the logs of the `perf-test` job in our [GitHub Actions workflow](https://github.com/livestorejs/livestore/actions/workflows/ci.yml). ## Reporting a performance issue We’re committed to transparency and continuous improvement. If you find performance gaps or regressions in your own usage, please [file an issue](https://github.com/livestorejs/livestore/issues/new) # [State of the project](https://dev.docs.livestore.dev/evaluation/state-of-the-project/) ## Overview LiveStore is based on years of research (see [Riffle](https://riffle.systems/essays/prelude/)) and is used as the foundation for ambitious apps such as [Overtone](https://overtone.pro). LiveStore has been in development since 2021 and is making good progress towards a stable release. LiveStore is not yet ready for all production scenarios. ## Current state LiveStore is currently in **beta** with most APIs being fairly stable (there might still be some breaking changes in coming releases). Most work is currently focussed on reliability and performance improvements. There is currently no specific timeline for a 1.0 release but we are making good progress in that direction. ### On breaking changes While LiveStore is in beta there can be three kinds of breaking changes: - Breaking API changes - Client storage format changes (whenever `liveStoreStorageFormatVersion` is updated) - Sync backend storage format changes (e.g. when a sync backend implementation changes the way how it stores data) We try our best to minimize breaking changes and to provide a migration path whenever possible. ## Roadmap See [GitHub issues](https://github.com/livestorejs/livestore/issues) for more details. Get in touch if you have any questions or feedback. ### 2025 Q3 - Adapter bug fixes & stability improvements - Performance improvements - Syncing latency & throughput - More testing ### Long-term - Eventlog compaction [#136](https://github.com/livestorejs/livestore/issues/136) - Support more syncing providers - Support more framework integrations - Support more platforms (e.g. Electron, Tauri) # [Technology comparison](https://dev.docs.livestore.dev/evaluation/technology-comparison/) ## Overview ## TLDR of what sets LiveStore apart - Uses combination of reactive, in-memory + synced, persisted SQLite for instant, synchronous queries - Based on event-sourcing methodologies - Client-centric (with great devtools) ## Other local-first/syncing technologies To compare LiveStore with other local-first/syncing technologies, please see the [Local-First Landscape](https://www.localfirst.fm/landscape) resource. ## LiveStore vs Redux LiveStore shares a lot of similarities with Redux in that sense that both are based on event-sourcing methodologies. Let's compare some of the core concepts: - Redux actions are similar to LiveStore events: Both are used to describe "things that have happened" - Redux views are similar to LiveStore's state (e.g. SQLite tables): Both are derived from the history of events/actions. - A major difference here is that LiveStore's state materialized as a SQLite database allows for a lot more flexibility via dynamic queries and aggregations vs Redux's static views. - Redux reducers are similar to LiveStore's materializers: Both are used to transform events/actions into a final state. - Both Redux and LiveStore are client-centric. - Both Redux and LiveStore provide powerful [devtools](/reference/devtools). While LiveStore can be used for the same use cases as Redux, LiveStore goes far Redux in the following ways: - LiveStore leverages SQLite for a more powerful state model allowing for flexible queries and aggregations with much simpler materialization logic. - LiveStore support client-persistence out of the box. - LiveStore comes with a built-in [sync engine](/reference/syncing) syncing events between clients. As a downside compared to Redux, LiveStore has a slightly larger bundle size. ## Other state management libraries - Zustand - Redux Toolkit (RTK) - MobX - Jotai - Xstate - Recoil - React Query # [Examples](https://dev.docs.livestore.dev/examples//) ## Overview ## Explore all examples [View all examples](https://github.com/livestorejs/livestore/tree/main/examples/standalone) ## Hosted demos ### Web - [TodoMVC React](https://web-todomvc.livestore.dev) / [Source](https://github.com/livestorejs/livestore/tree/main/examples/standalone/web-todomvc) - [TodoMVC React + Sync CF](https://web-todomvc-sync-cf.livestore.dev) / [Source](https://github.com/livestorejs/livestore/tree/main/examples/standalone/web-todomvc-sync-cf) - [Linearlite React](https://web-linearlite.livestore.dev) / [Source](https://github.com/livestorejs/livestore/tree/main/examples/standalone/web-linearlite) # [Expo](https://dev.docs.livestore.dev/getting-started/expo/) ## Overview import { Code, Steps, Tabs, TabItem } from '@astrojs/starlight/components' import { makeTiged, versionNpmSuffix } from '../../../../data.js' import { MIN_NODE_VERSION } from '../../../../../CONSTANTS.ts' import babelConfigCode from '../../../../../examples/standalone/expo-todomvc-sync-cf/babel.config.js?raw' import metroConfigCode from '../../../../../examples/standalone/expo-todomvc-sync-cf/metro.config.js?raw' import schemaCode from '../../../../../examples/standalone/expo-todomvc-sync-cf/src/livestore/schema.ts?raw' import rootCode from '../../../../../examples/standalone/expo-todomvc-sync-cf/src/Root.tsx?raw' import headerCode from '../../../../../examples/standalone/expo-todomvc-sync-cf/src/components/NewTodo.tsx?raw' import mainSectionCode from '../../../../../examples/standalone/expo-todomvc-sync-cf/src/components/ListTodos.tsx?raw' export const CODE = { babelConfig: babelConfigCode, metroConfig: metroConfigCode, schema: schemaCode, root: rootCode, header: headerCode, mainSection: mainSectionCode, } {/* We're adjusting the package to use the dev version on the dev branch */} export const manualInstallDepsStr = [ '@livestore/devtools-expo' + versionNpmSuffix, '@livestore/adapter-expo' + versionNpmSuffix, '@livestore/livestore' + versionNpmSuffix, '@livestore/react' + versionNpmSuffix, '@livestore/sync-cf' + versionNpmSuffix, '@livestore/peer-deps' + versionNpmSuffix, 'expo-sqlite', ].join(' ') ### Prerequisites - Recommended: Bun 1.2 or higher - Node.js {MIN_NODE_VERSION} or higher To use [LiveStore](/) with [Expo](https://docs.expo.dev/), ensure your project has the [New Architecture](https://docs.expo.dev/guides/new-architecture/) enabled. This is required for transactional state updates. ### Option A: Quick start For a quick start we recommend using our template app following the steps below. For existing projects see [Existing project setup](#existing-project-setup). 1. **Set up project from template** Replace `livestore-app` with your desired app name. 2. **Install dependencies** It's strongly recommended to use `bun` or `pnpm` for the simplest and most reliable dependency setup (see [note on package management](/misc/package-management) for more details). ```bash bun install ``` ```bash pnpm install --node-linker=hoisted ``` Make sure to use `--node-linker=hoisted` when installing dependencies in your project or add it to your `.npmrc` file. ``` # .npmrc nodeLinker=hoisted ``` Hopefully Expo will also support non-hoisted setups in the future. ```bash npm install ``` When using `yarn`, make sure you're using Yarn 4 or higher with the `node-modules` linker. ```bash yarn set version stable yarn config set nodeLinker node-modules yarn install ``` Pro tip: You can use [direnv](https://direnv.net/) to manage environment variables. 3. **Run the app** In a new terminal, start the Cloudflare Worker (for the sync backend): ### Option B: Existing project setup \{#existing-project-setup\} 1. **Install dependencies** 2. **Add Vite meta plugin to babel config file** LiveStore Devtools uses Vite. This plugin emulates Vite's `import.meta.env` functionality. In your `babel.config.js` file, add the plugin as follows: 3. **Update Metro config** Add the following code to your `metro.config.js` file: ## Define Your Schema Create a file named `schema.ts` inside the `src/livestore` folder. This file defines your LiveStore schema consisting of your app's event definitions (describing how data changes), derived state (i.e. SQLite tables), and materializers (how state is derived from events). Here's an example schema: ## Add the LiveStore Provider To make the LiveStore available throughout your app, wrap your app's root component with the `LiveStoreProvider` component from `@livestore/react`. This provider manages your app’s data store, loading, and error states. Here's an example: ### Commit events After wrapping your app with the `LiveStoreProvider`, you can use the `useStore` hook from any component to commit events. Here's an example: ## Queries To retrieve data from the database, first define a query using `queryDb` from `@livestore/livestore`. Then, execute the query with the `useQuery` hook from `@livestore/react`. Consider abstracting queries into a separate file to keep your code organized, though you can also define them directly within components if preferred. Here's an example: ## Devtools To open the devtools, run the app and from your terminal press `shift + m`, then select LiveStore Devtools and press `Enter`. ![Expo Terminal Screenshot](../../../assets/devtools-terminal-expo.png) This will open the devtools in a new tab in your default browser. ![Devtools Browser Screenshot](../../../assets/devtools-browser-view.png) Use the devtools to inspect the state of your LiveStore database, execute events, track performance, and more. ## Database location ### With Expo Go To open the database in Finder, run the following command in your terminal: ```bash open $(find $(xcrun simctl get_app_container booted host.exp.Exponent data) -path "*/Documents/ExponentExperienceData/*livestore-expo*" -print -quit)/SQLite ``` ### With development builds For development builds, the app SQLite database is stored in the app's Library directory. Example: `/Users//Library/Developer/CoreSimulator/Devices//data/Containers/Data/Application//Documents/SQLite/app.db` To open the database in Finder, run the following command in your terminal: ```bash open $(xcrun simctl get_app_container booted [APP_BUNDLE_ID] data)/Documents/SQLite ``` Replace `[APP_BUNDLE_ID]` with your app's bundle ID. e.g. `dev.livestore.livestore-expo`. ## Further notes - LiveStore doesn't yet support Expo Web (see [#130](https://github.com/livestorejs/livestore/issues/130)) # [Node](https://dev.docs.livestore.dev/getting-started/node/) ## Overview import { Steps, Tabs, TabItem, Code } from '@astrojs/starlight/components'; import { makeTiged } from '../../../../data.js' ## Minimal example ```ts import { makeAdapter } from '@livestore/adapter-node' import { createStorePromise } from '@livestore/livestore' import { tables, schema } from './livestore/schema.js' const adapter = makeAdapter({ storage: { type: 'fs' }, // sync: { backend: makeCfSync({ url: '...' }) }, }) const store = await createStorePromise({ adapter, schema }) const todos = store.query(tables.todos) ``` ### Option A: Quick start For a quick start, we recommend using our template app following the steps below. {/* For existing projects, see [Existing project setup](#existing-project-setup). */} 1. **Set up project from template** Replace `livestore-app` with your desired app name. 2. **Install dependencies** It's strongly recommended to use `bun` or `pnpm` for the simplest and most reliable dependency setup (see [note on package management](/misc/package-management) for more details). Pro tip: You can use [direnv](https://direnv.net/) to manage environment variables. 3. **Run dev environment** # [When to use LiveStore (and when not)](https://dev.docs.livestore.dev/evaluation/when-livestore/) ## Overview Choosing a data layer for a local-first app is a big decision and should be considered carefully. On a high level, LiveStore can be a good fit if ... - you are looking for a principled data layer that works across platforms - you want to use SQLite for your queries - you like [event sourcing](/evaluation/event-sourcing) to model data changes - you are working on a new app as LiveStore doesn't yet provide a way to [re-use an existing database](/misc/faq#existing-database) - the current [state of the project](/evaluation/state-of-the-project) aligns with your own timeline and requirements ## Evaluation exercise A great way to evaluate whether LiveStore is a good fit for your application, is by trying to model your application events (and optionally state) schema. This exercise can be done in a few minutes and can give you a good indication of whether LiveStore is a good fit for your application. ### Example: Calendar/scheduling app Let's say you are building a calendar/scheduling app, your events might include: - `AppointmentScheduled` - `AppointmentRescheduled` - `AppointmentCancelled` - `ParticipantInvitedToAppointment` - `ParticipantRespondedToInvite` From this you might want to derive the following state (modeled as SQLite tables): - `Appointment` - `id` - `title` - `description` - `participants` - `Participant` - `id` - `name` - `email` ## Great use cases for LiveStore - High-performance desktop/web/mobile apps - e.g. productivity apps like - AI agents - Apps that need ... - solid offline support - audit logs ## Benefits of LiveStore - Unified data layer combining local reactive state with globally synced data - Easy to ... - reason about - debug - test - evolve - operate ## Reasons when not to use LiveStore - You have an existing database which is the source of truth of your data. (Better use [Zero](https://zero.rocicorp.dev) or [ElectricSQL](https://www.electricsql.com) for this.) - Your app data is highly connected across users (like a social network / marketplace / etc.) or modeling your data via read-write model separation/event sourcing doesn't seem feasible. - You want to build a more traditional client-server application with your primary data source being a remote server. - You want a full-stack batteries-included solution (e.g. auth, storage, etc.). (Technologies like [Jazz](https://jazz.tools) or [Instant](https://instantdb.com) might be a better fit.) - You don't like to model your data via read-write model separation/event sourcing or the trade-offs it involves. - You're a new developer and are just getting started. LiveStore is a relatively advanced technology with many design trade-offs that might make most sense after you have already experienced some of the problems LiveStore is trying to solve. - You want to keep your app bundle size as small as possible. LiveStore adds a few hundred kB to your app bundle size (mostly due to bundling SQLite). ## Considerations ### Database constraints - All the client app data should fit into a in-memory SQLite database - Depending on the target device having databases up to 1GB in size should be okay. - If you you have more data, you can consider segmenting your database into multiple SQLite database (e.g. segmented per project, workspace, document, ...). - You can either use the `storeId` option for the segmentation or there could also be a way to use the [SQLite attach feature](https://www.sqlite.org/lang_attach.html) to dynamically attach/detach databases. ### Syncing LiveStore's syncing system is designed for small/medium-level concurrency scenarios (e.g. 10s / low 100s of users collaborating on the same thing for a given eventlog). - Collaboration on multiple different eventlogs concurrently is supported and should be used to "scale horizontally". ### Other considerations - How data flows / what's the source of truth? # [Getting started with LiveStore + React](https://dev.docs.livestore.dev/getting-started/react-web/) ## Overview import { Steps, Tabs, TabItem, Code } from '@astrojs/starlight/components'; import { makeTiged, versionNpmSuffix } from '../../../../data.js' import { MIN_NODE_VERSION, LIVESTORE_WA_SQLITE_VERSION } from '../../../../../CONSTANTS.ts' import viteConfigCode from '../../../../../examples/standalone/web-todomvc-sync-cf/vite.config.js?raw' import schemaCode from '../../../../../examples/standalone/web-todomvc-sync-cf/src/livestore/schema.ts?raw' import workerCode from '../../../../../examples/standalone/web-todomvc-sync-cf/src/livestore.worker.ts?raw' import rootCode from '../../../../../examples/standalone/web-todomvc-sync-cf/src/Root.tsx?raw' import headerCode from '../../../../../examples/standalone/web-todomvc-sync-cf/src/components/Header.tsx?raw' import mainSectionCode from '../../../../../examples/standalone/web-todomvc-sync-cf/src/components/MainSection.tsx?raw' export const CODE = { viteConfig: viteConfigCode, schema: schemaCode, worker: workerCode, root: rootCode, header: headerCode, mainSection: mainSectionCode, } {/* We're adjusting the package to use the dev version on the dev branch */} export const manualInstallDepsStr = [ '@livestore/livestore' + versionNpmSuffix, '@livestore/wa-sqlite@' + LIVESTORE_WA_SQLITE_VERSION, '@livestore/adapter-web' + versionNpmSuffix, '@livestore/react' + versionNpmSuffix, '@livestore/peer-deps' + versionNpmSuffix, '@livestore/sync-cf' + versionNpmSuffix, '@livestore/devtools-vite' + versionNpmSuffix, ].join(' ') ## Prerequisites - Recommended: Bun 1.2 or higher - Node.js {MIN_NODE_VERSION} or higher ### Option A: Quick start For a quick start, we recommend using our template app following the steps below. For existing projects, see [Existing project setup](#existing-project-setup). 1. **Set up project from template** Replace `livestore-app` with your desired app name. 2. **Install dependencies** It's strongly recommended to use `bun` or `pnpm` for the simplest and most reliable dependency setup (see [note on package management](/misc/package-management) for more details). Pro tip: You can use [direnv](https://direnv.net/) to manage environment variables. 3. **Run dev environment** 4. **Open browser** Open `http://localhost:60000` in your browser. You can also open the devtools by going to `http://localhost:60000/_livestore`. ### Option B: Existing project setup \{#existing-project-setup\} 1. **Install dependencies** 2. **Update Vite config** Add the following code to your `vite.config.js` file: ## Define Your Schema Create a file named `schema.ts` inside the `src/livestore` folder. This file defines your LiveStore schema consisting of your app's event definitions (describing how data changes), derived state (i.e. SQLite tables), and materializers (how state is derived from events). Here's an example schema: ## Create the LiveStore Worker Create a file named `livestore.worker.ts` inside the `src/livestore` folder. This file will contain the LiveStore web worker. When importing this file, make sure to add the `?worker` extension to the import path to ensure that Vite treats it as a worker file. ## Add the LiveStore Provider To make the LiveStore available throughout your app, wrap your app's root component with the `LiveStoreProvider` component from `@livestore/react`. This provider manages your app's data store, loading, and error states. Here's an example: ### Commit events After wrapping your app with the `LiveStoreProvider`, you can use the `useStore` hook from any component to commit events. Here's an example: ## Queries To retrieve data from the database, first define a query using `queryDb` from `@livestore/livestore`. Then, execute the query with the `useQuery` hook from `@livestore/react`. Consider abstracting queries into a separate file to keep your code organized, though you can also define them directly within components if preferred. Here's an example: # [Solid](https://dev.docs.livestore.dev/getting-started/solid/) ## Overview TODO # [Getting started with LiveStore + Vue](https://dev.docs.livestore.dev/getting-started/vue/) ## Overview import { Steps, Tabs, TabItem, Code } from '@astrojs/starlight/components'; import { makeTiged, versionNpmSuffix } from '../../../../data.js' import { MIN_NODE_VERSION, LIVESTORE_WA_SQLITE_VERSION } from '../../../../../CONSTANTS.ts' import viteConfigCode from '../../../../../examples/standalone/web-todomvc-sync-cf/vite.config.js?raw' import schemaCode from '../../../../../examples/standalone/web-todomvc-sync-cf/src/livestore/schema.ts?raw' import workerCode from '../../../../../examples/standalone/web-todomvc-sync-cf/src/livestore.worker.ts?raw' import rootCode from '../../../../../examples/standalone/web-todomvc-sync-cf/src/Root.tsx?raw' import headerCode from '../../../../../examples/standalone/web-todomvc-sync-cf/src/components/Header.tsx?raw' import mainSectionCode from '../../../../../examples/standalone/web-todomvc-sync-cf/src/components/MainSection.tsx?raw' export const CODE = { viteConfig: viteConfigCode, schema: schemaCode, worker: workerCode, root: rootCode, header: headerCode, mainSection: mainSectionCode, } {/* We're adjusting the package to use the dev version on the dev branch */} export const manualInstallDepsStr = [ '@livestore/livestore' + versionNpmSuffix, '@livestore/wa-sqlite@' + LIVESTORE_WA_SQLITE_VERSION, '@livestore/adapter-web' + versionNpmSuffix, '@livestore/utils' + versionNpmSuffix, '@livestore/peer-deps' + versionNpmSuffix, '@livestore/devtools-vite' + versionNpmSuffix, 'slashv/vue-livestore' + versionNpmSuffix, ].join(' ') ## Prerequisites - Recommended: Bun 1.2 or higher - Node.js {MIN_NODE_VERSION} or higher ## About Vue integration Vue integration is still in beta and being incubated as a separate repository. Please direct any issues or contributions to [Vue LiveStore](https://github.com/slashv/vue-livestore) ## Option A: Quick start For a quick start, we recommend referencing the [playground](https://github.com/slashv/vue-livestore/tree/main/playground) folder in the Vue LiveStore repository. ## Option B: Existing project setup \{#existing-project-setup\} 1. **Install dependencies** It's strongly recommended to use `bun` or `pnpm` for the simplest and most reliable dependency setup (see [note on package management](/misc/package-management) for more details). 2. **Update Vite config** Add the following code to your `vite.config.js` file: ```ts import { livestoreDevtoolsPlugin } from '@livestore/devtools-vite' import { defineConfig } from 'vite' import vue from '@vitejs/plugin-vue' import vueDevTools from 'vite-plugin-vue-devtools' export default defineConfig({ plugins: [ vue(), vueDevTools(), livestoreDevtoolsPlugin({ schemaPath: './src/livestore/schema.ts' }), ], worker: { format: 'es' }, }) ``` ### Define Your Schema Create a file named `schema.ts` inside the `src/livestore` folder. This file defines your LiveStore schema consisting of your app's event definitions (describing how data changes), derived state (i.e. SQLite tables), and materializers (how state is derived from events). Here's an example schema: ### Create the LiveStore Worker Create a file named `livestore.worker.ts` inside the `src/livestore` folder. This file will contain the LiveStore web worker. When importing this file, make sure to add the `?worker` extension to the import path to ensure that Vite treats it as a worker file. ### Add the LiveStore Provider To make the LiveStore available throughout your app, wrap your app's root component with the `LiveStoreProvider` component from `vue-livestore`. This provider manages your app's data store, loading, and error states. Here's an example: ```vue ``` ### Commit events After wrapping your app with the `LiveStoreProvider`, you can use the `useStore` hook from any component to commit events. Here's an example: ```vue ``` ### Queries To retrieve data from the database, first define a query using `queryDb` from `@livestore/livestore`. Then, execute the query with the `useQuery` hook from `@livestore/react`. Consider abstracting queries into a separate file to keep your code organized, though you can also define them directly within components if preferred. Here's an example: ```vue ``` # [Code of Conduct](https://dev.docs.livestore.dev/misc/CODE_OF_CONDUCT/) ## Overview ## Our Pledge We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. ## Our Standards Examples of behavior that contributes to a positive environment for our community include: * Demonstrating empathy and kindness toward other people * Being respectful of differing opinions, viewpoints, and experiences * Giving and gracefully accepting constructive feedback * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience * Focusing on what is best not just for us as individuals, but for the overall community Examples of unacceptable behavior include: * The use of sexualized language or imagery, and sexual attention or advances of any kind * Trolling, insulting or derogatory comments, and personal or political attacks * Public or private harassment * Publishing others' private information, such as a physical or email address, without their explicit permission * Other conduct which could reasonably be considered inappropriate in a professional setting ## Enforcement Responsibilities Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate. ## Scope This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. ## Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [contact@livestore.dev][Contact]. All complaints will be reviewed and investigated promptly and fairly. All community leaders are obligated to respect the privacy and security of the reporter of any incident. ## Enforcement Guidelines Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: ### 1. Correction **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. **Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. ### 2. Warning **Community Impact**: A violation through a single incident or series of actions. **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. ### 3. Temporary Ban **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior. **Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. ### 4. Permanent Ban **Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. **Consequence**: A permanent ban from any sort of public interaction within the community. ## Attribution This Code of Conduct is adapted from the [Contributor Covenant][Homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC]. For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][Translations]. [Homepage]: https://www.contributor-covenant.org [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html [Mozilla CoC]: https://github.com/mozilla/diversity [FAQ]: https://www.contributor-covenant.org/faq [Translations]: https://www.contributor-covenant.org/translations [Contact]: mailto:contact@livestore.dev # [Frequently Asked Questions](https://dev.docs.livestore.dev/misc/FAQ/) ## Overview ### Does LiveStore have optimistic updates? Yes and no. LiveStore doesn't have the concept of optimistic updates as you might know from libraries like [React Query](https://tanstack.com/query/latest/docs/framework/react/guides/optimistic-updates), however, any data update in LiveStore is automatically optimistic without the developer having to implement any special logic. This provides the benefits of optimistic updates without the extra complexity by manually having to implement the logic for each individual data update (which can be very error prone). ### Does LiveStore have database transactions? LiveStore runs on the client-side and handles transactions differently than traditional server-side databases. While materializers automatically run in transactions, global transactional behavior (often called "online transactions") needs to be explicitly modeled in your application logic. ### Can I use an ORM or query builder with LiveStore? It's possible to use most ORMs/query builders with LiveStore (as long as they are able to synchronously generate SQL statements). You should also give the built-in LiveStore query builder a try. See [the ORM page](/patterns/orm) for more information. ### Is there a company behind LiveStore? How does LiveStore make money? LiveStore is developed by [Johannes Schickling](https://github.com/schickling) and has been incubated as the foundation of [Overtone](https://overtone.pro) (a local-first music app). The plan is to keep the development of LiveStore as sustainable as possible via sponsorships and other paths (e.g. commercial licenses, paid consulting, premium devtools, etc). ### Is there a hosted sync backend provided by LiveStore? No, LiveStore is designed to be self-hosted or be used with a 3rd party sync backend. ### Can I use my existing database with LiveStore? {#existing-database} Not currently. LiveStore is built around the idea of event-sourcing which separates reads and writes. This means LiveStore isn't syncing your database directly but only the events that are used to materialize the database making sure it's kept in sync across clients. However, we might provide support for this in the future depending on demand. # [Community](https://dev.docs.livestore.dev/misc/community/) ## Overview import { DISCORD_INVITE_URL } from '../../../../../CONSTANTS.js' import { officeHours } from '../../../../data.js' ## Discord You can join the Discord server here. ## Office hours You can join future office hour events [here](https://lu.ma/livestore). { officeHours.map((url) => (