`react-doctor/zustand-no-get-during-initialization`

Zustand get() called during store initialization

Category: Bugs
Severity: error
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: react, zustand, zustand:1
Default: Enabled

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Confirm the reported code matches react-doctor/zustand-no-get-during-initialization. Compare it with the Before example and verify the same API, framework, and execution context. Treat it as a false positive only when one of those conditions differs.

Compare the code

The corrected pattern shows a focused way to address the diagnostic.

Reported pattern

import { create } from "zustand";

interface Item {
  id: string;
}

interface ItemStore {
  items: Item[];
  selectedId?: string;
}

const createItemStore = (initialItems: Item[]) =>
  create<ItemStore>((_setState, getState) => ({
    items: initialItems,
    selectedId: getState().items[0]?.id,
  }));

Corrected pattern

import { create } from "zustand";

interface Item {
  id: string;
}

interface ItemStore {
  items: Item[];
  selectedId?: string;
}

const createItemStore = (initialItems: Item[]) =>
  create<ItemStore>(() => ({
    items: initialItems,
    selectedId: initialItems[0]?.id,
  }));

How to fix

Use the corrected pattern as a reference. Preserve behavior that the rule does not require you to change.

Copyable fix prompt

Copy this self-contained prompt into your coding agent after you confirm the diagnostic.

Fix every confirmed react-doctor/zustand-no-get-during-initialization diagnostic in the current repository. Required change: - Move the read into a deferred store action or derive the initial value without calling get().

Reference transformation:Before:

import { create } from "zustand";

interface Item {
  id: string;
}

interface ItemStore {
  items: Item[];
  selectedId?: string;
}

const createItemStore = (initialItems: Item[]) =>
  create<ItemStore>((_setState, getState) => ({
    items: initialItems,
    selectedId: getState().items[0]?.id,
  }));

After:

import { create } from "zustand";

interface Item {
  id: string;
}

interface ItemStore {
  items: Item[];
  selectedId?: string;
}

const createItemStore = (initialItems: Item[]) =>
  create<ItemStore>(() => ({
    items: initialItems,
    selectedId: initialItems[0]?.id,
  }));

Constraints: - Confirm the reported code matches the Before pattern. - Make the smallest change that fixes the root cause. - Preserve behavior and interfaces unrelated to this diagnostic. - Reuse existing project components, utilities, and conventions. - Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations. - Adapt identifiers and framework details instead of copying blindly. - Do not disable the rule or suppress matching code. - Confirm this rule is enabled for the project: react, zustand, zustand:1. Verification: - Run focused tests for the changed behavior. - Run React Doctor and confirm this diagnostic no longer appears. - Report the files changed and any checks you could not run.

More Bugs rules from the rules reference:

react-doctor/zustand-no-mutating-state: Zustand state mutated in place
react-doctor/zustand-no-whole-store-destructure: Whole Zustand store subscribed during render
react-doctor/activity-wraps-effect-heavy-subtree: Audit the `<Activity>` subtree: every hide/show cycle tears down and recreates every `useEffect`/`useLayoutEffect` inside, so move subscriptions and effect-driven setState chains outside the boundary or pre-resolve the data above it.
react-doctor/button-has-type: Set type="button" (or "submit"/"reset") explicitly on every <button> so it never defaults to submit.
react-doctor/checked-requires-onchange-or-readonly: Pair `checked` with `onChange={…}` (controlled) or `readOnly` (display-only), and never combine `checked` with `defaultChecked`.

react-doctor/zustand-no-get-during-initialization