Update dependency @tanstack/react-db to v0.1.67

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@tanstack/react-db (source)	0.1.52 → 0.1.67

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

TanStack/db (@​tanstack/react-db)

v0.1.67

Compare Source

Patch Changes

• Updated dependencies [05130f2]:
  • @​tanstack/db@​0.5.23

v0.1.66

Compare Source

Patch Changes

• Updated dependencies [f9b741e]:
  • @​tanstack/db@​0.5.22

v0.1.65

Compare Source

Patch Changes

• Updated dependencies [6745ed0, 1b22e40, 7a2cacd, bdf9405]:
  • @​tanstack/db@​0.5.21

v0.1.64

Compare Source

Patch Changes

• Updated dependencies []:
  • @​tanstack/db@​0.5.20

v0.1.63

Compare Source

Patch Changes

• Updated dependencies [29033b8, 888ad6a]:
  • @​tanstack/db@​0.5.19

v0.1.62

Compare Source

Patch Changes

• Updated dependencies [c1247e8]:
  • @​tanstack/db@​0.5.18

v0.1.61

Compare Source

Patch Changes

• Improve runtime error message and documentation when useLiveSuspenseQuery receives undefined from query callback. (#​860)

  Following TanStack Query's useSuspenseQuery design, useLiveSuspenseQuery intentionally does not support disabled queries (when callback returns undefined or null). This maintains the type guarantee that data is always T (not T | undefined), which is a core benefit of using Suspense.

  What changed:

  1. Improved runtime error message with clear guidance:

  useLiveSuspenseQuery does not support disabled queries (callback returned undefined/null).
  The Suspense pattern requires data to always be defined (T, not T | undefined).
  Solutions:
  1) Use conditional rendering - don't render the component until the condition is met.
  2) Use useLiveQuery instead, which supports disabled queries with the 'isEnabled' flag.
  

  2. Enhanced JSDoc documentation with detailed @remarks section explaining the design decision, showing both incorrect (❌) and correct (✅) patterns

  Why this matters:

  // ❌ This pattern doesn't work with Suspense queries:
  const { data } = useLiveSuspenseQuery(
    (q) => userId
      ? q.from({ users }).where(({ users }) => eq(users.id, userId)).findOne()
      : undefined,
    [userId]
  )
  
  // ✅ Instead, use conditional rendering:
  function UserProfile({ userId }: { userId: string }) {
    const { data } = useLiveSuspenseQuery(
      (q) => q.from({ users }).where(({ users }) => eq(users.id, userId)).findOne(),
      [userId]
    )
    return <div>{data.name}</div> // data is guaranteed non-undefined
  }
  
  function App({ userId }: { userId?: string }) {
    if (!userId) return <div>No user selected</div>
    return <UserProfile userId={userId} />
  }
  
  // ✅ Or use useLiveQuery for conditional queries:
  const { data, isEnabled } = useLiveQuery(
    (q) => userId
      ? q.from({ users }).where(({ users }) => eq(users.id, userId)).findOne()
      : undefined,
    [userId]
  )

  This aligns with TanStack Query's philosophy where Suspense queries prioritize type safety and proper component composition over flexibility.

• Updated dependencies [f795a67, d542667, 6503c09, b1cc4a7]:

  • @​tanstack/db@​0.5.17

v0.1.60

Compare Source

Patch Changes

• Updated dependencies [41308b8]:
  • @​tanstack/db@​0.5.16

v0.1.59

Compare Source

Patch Changes

• Updated dependencies [32ec4d8]:
  • @​tanstack/db@​0.5.15

v0.1.58

Compare Source

Patch Changes

• Updated dependencies [26ed0aa]:
  • @​tanstack/db@​0.5.14

v0.1.57

Compare Source

Patch Changes

• Updated dependencies [8ed7725, 01452bf]:
  • @​tanstack/db@​0.5.13

v0.1.56

Compare Source

Patch Changes

• Updated dependencies [b3b1940, 09da081, 86ad40c]:
  • @​tanstack/db@​0.5.12

v0.1.55

Compare Source

Patch Changes

• Fixed isReady to return true for disabled queries in useLiveQuery/injectLiveQuery across all framework packages. When a query function returns null or undefined (disabling the query), there's no async operation to wait for, so the hook should be considered "ready" immediately. (#​886)

  Additionally, all frameworks now have proper TypeScript overloads that explicitly support returning undefined | null from query functions, making the disabled query pattern type-safe.

  This fixes the common pattern where users conditionally enable queries and don't want to show loading states when the query is disabled.

• Updated dependencies [c4b9399, a1a484e]:

  • @​tanstack/db@​0.5.11

v0.1.54

Compare Source

Patch Changes

• Updated dependencies [1d19d22, b3e4e80]:
  • @​tanstack/db@​0.5.10

v0.1.53

Compare Source

Patch Changes

• Updated dependencies [5f474f1]:
  • @​tanstack/db@​0.5.9

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.