Observe IndexedDB data in your React component. Make the component re-render when the observed data changes.

See Also



npm i react dexie dexie-react-hooks


yarn add react dexie dexie-react-hooks


export function useLiveQuery<T, TDefault=undefined> (
  querier: () => Promise<T> | T,
  deps?: any[], // deps argument in useEffect() but defaults to empty array.
  defaultResult?: TDefault // Default value returned while data is loading
) : T | TDefault;

Parameter Description
querier Function that returns a final result (Promise)
deps Variables that querier is dependent on (similar to the deps argument in useEffect()).
defaultResult Result returned on initial render - before the promise have resolved.

Rules for the querier function

  • Don’t call asynchronous API:s from it except Dexie’s APIs.
  • If you really need to call other async API’s (such as fetch() or webCrypto), wrap the returned promise through Promise.resolve(). There’s an example later in this page on how to do that.

Simple Example

import React from "react";
import Dexie from "dexie";
import { useLiveQuery } from "dexie-react-hooks";
import { db } from "./db";

// React component
export function OldFriendsList() {
  const friends = useLiveQuery(
    () => db.friends
  if (!friends) return null; // Still loading.
  return <ul>
    { =>
        <li key={}>
          {}, {friend.age}

See also this stackoverflow question (and answer) on how to determine whether a response is still loading or has returned an undefined result

Persistent State Manager

The useLiveQuery() hook does not only load data - it observes the query for changes. This means that you can use Dexie as a persistent and RAM-sparse state manager in your React application since you don’t keep entire database in RAM. If you add, update or delete a friend using Dexie methods for that (such as Table.add, Table.update(), Table.delete(), …etc), any component that observes the affected data will automatically rerender.

Fine grained observation

The observation is as fine-grained as it can possibly be - queries that would be affected by a modification will rerender - others not (with some exceptions - false positives happen but never false negatives). This is also true if your querier callback performs a series of awaited queries or multiple in parallel using Promise.all(). It can even contain if-statements or other conditional paths within it, determining additional queries to make before returning a final result - still, observation will function and never miss an update. No matter how simple or complex the query is - it will be monitored in detail so that if a single part of the query is affected by a change, the querier will be executed and the component will rerender.


  • Changes must have been made using Dexie.js: This hook will only observe changes made using Dexie.js. Changes from devtools or another IndexedDB wrapper will not be observed. However, as long as changes were made using Dexie.js version 3.1 or later - be it from a service worker, web worker, other tab or window, the hook will react instantly to any changes affecting the query it observes. This functionality is built-in into Dexie.js itself and a react app will also be able to observe changes made from another app that does not have dexie-react-hooks installed. Since there is no native API for this kind of observation, Dexie made it a first-class citizen for all that use Dexie.js as persistence layer.
  • Same origin only: IndexedDB is a per-origin database, meaning that offline data stored for one website cannot read data for another website unless they share the same origin. useLiveQuery() will naturally have the same boundary between origins. Syncing data between origins, clients and different browsers or devices require another solution and can be accomplished using our addon dexie-cloud-addon and our commercial service Dexie Cloud.
  • Avoid calling other API’s from your querier callback. See Calling non-Dexie APIs from querier below.

Enhanced Example

This example shows that…

  • you can observe the result of an arbitrary function that queries Dexie
  • you can use a state from a useState() result within your querier function (just need to mention it in the deps array)
  • the component will re-render if the data you are querying change
  • the component will re-render if in-parameter to the query change.
  • the query will change when state change.
import React, { useState } from "react";
import { useLiveQuery } from "dexie-react-hooks";
import { db } from "../db";

export function FriendList() {
  const [maxAge, setMaxAge] = useState(21);

  // Query friends within a certain range decided by state:
  const friends = useLiveQuery(
    () => db.friends.where("age").belowOrEqual(maxAge).sortBy("id"),
    [maxAge] // because maxAge affects query!

  // Example of another query in the same component.
  const friendCount = useLiveQuery(() => db.friends.count());

  // If default values are returned, queries are still loading:
  if (!friends || friendCount === undefined) return null;

  return (
        Your have <b>{friendCount}</b> friends in total.
        Please enter max age to query:
          onChange={(ev) => setMaxAge(parseInt(, 10))}
        { => (
          <li key={}>
            {}, {friend.age}
              onClick={() =>
                db.friends.where({ id: }).modify((f) => ++f.age)

Open in codesandbox


The expression passed to useLiveQuery() must be a function that returns a promise. If you need to decouple your component from the db, you can provide the querying functions as callbacks instead:

export function FriendList({getFriendCount, getFriendsByAge, onBirthdayClick}) {

  const friendCount = useLiveQuery(getFriendCount);

  const friends = useLiveQuery(
    () => getFriendsByAge(maxAge), [maxAge]

      // And the button's onClick event:
      <button ... onClick={()=>onBirthdayClick(friend)}>...</button>

// ...and implement the callback elsewhere...

function App () {
   const getFriendCount = () => db.friends.count();

   const getFriendsByAge = maxAge =>

   const onBirthdayClick = friend =>
    db.friends.where({ id: }).modify(f => ++f.age);
  return <FriendList
    onBirthdayClick={onBirthdayClick} />;

Calling non-Dexie API:s from querier

If your querier callback needs to call asynchronous non-Dexie APIs to resolve its result, the promises returned by those non-Dexie API:s needs to be wrapped using Promise.resolve(). This is needed in order to keep the observation context alive between async calls. Even though APIs like fetch(), webCrypto etc already returns promises, this is still needed in order for useLiveQuery() to function properly. It might feel unnecessary to wrap it with Promise.resolve() when it’s already a promise being returned, but this is a rule that needs to be followed when using useLiveQuery() with non-Dexie APIs. As of Dexie 3.2.0, you might not notice any warning or error if not following this rule but in a future version of Dexie, it might start throwing some explanatory error if this rule has been forgotten.

function MyComponent(id) {
  const friendWithMetaData = useLiveQuery(async () => {
    // Normal Dexie call:
    const friend = await db.friends.get(id);
    // Calling non-Dexie API - always wrap with Promise.resolve():
    try {
      const friendMetaData = await Promise.resolve (
        // Ok to call fetch if we wrap it with Promise.resolve()
        fetch(friend.metaDataUrl).then(res => res.json())
      friend.metaData = friendMetaData;
    } catch (error) {
      friend.metaData = null;
    return friend;
  }, [id]);
  return <>
    <p>Name: {}</p>
    <p>FooBar: {friendWithMetaData.metaData?.fooBar}</p>


Another sample using useLiveQuery() on Stackblitz

The sample from this page in CodeSandbox

See also


A blog post about this


Table of Contents