New
Introducing React Bench, see how different models perform on React code

react-doctor/valtio-no-proxy-read-in-render

Valtio proxy read during render

  • Category: Bugs
  • Severity: warn
  • Source: oxlint-plugin-react-doctor
  • Framework: global
  • Enabled when: react, valtio:1
  • Default: Enabled

Validate the diagnostic

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

Confirm the reported code matches react-doctor/valtio-no-proxy-read-in-render. 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 { useSnapshot } from "valtio";

const Counter = () => {
  const snapshot = useSnapshot(store);
  return <button type="button">{store.count}</button>;
};

Corrected pattern

import { useSnapshot } from "valtio";

const Counter = () => {
  const snapshot = useSnapshot(store);
  return <button type="button">{snapshot.count}</button>;
};

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/valtio-no-proxy-read-in-render diagnostic in the current repository. Required change: - Read reactive render values from useSnapshot. Reserve the mutable proxy for event handlers, effects, and other callbacks that need the latest value.
Reference transformation:Before:
import { useSnapshot } from "valtio";

const Counter = () => {
  const snapshot = useSnapshot(store);
  return <button type="button">{store.count}</button>;
};
After:
import { useSnapshot } from "valtio";

const Counter = () => {
  const snapshot = useSnapshot(store);
  return <button type="button">{snapshot.count}</button>;
};
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, valtio: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: