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

react-doctor/jsx-no-constructed-context-values

Memoize the context value with useMemo/useCallback or hoist it outside the render

Status
Active
Category
Performance
Assessment
Evidence-required risk
Required evidence
source code, runtime behavior, measurement
Default configuration
Enabled
Default severity
warn
Show technical metadata
Scope
All supported frameworks
Active when
always
Disabled when
react-compiler
Requirements
react
Tags
react-jsx-only
Priority
56 (P2)
Source
oxlint-plugin-react-doctor
Rule set
oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
On this page

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Fires on a <X.Provider value={…}> opening element sitting inside a function (a render) when the value expression is constructed fresh each render: an object, array, arrow/function/class expression, new expression, JSX element/fragment, or a conditional/logical whose branches resolve to any of those. Every such provider re-renders all consumers on each parent render because the value gets a new identity. False positive boundary: it only inspects literal construction at the JSX site: an identifier (value={foo}) is never flagged even when foo is an inline {} or an unmemoized useMemo(() => …) with no deps, and spread props (<X.Provider {...rest}>) and member accesses (value={ctx.current}) are likewise not checked, so a confirmed finding is one where the literal sits directly in the attribute.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

  • Confirmed failure: The required evidence establishes the violation.
  • Rejected: A documented exception or false-positive predicate applies.
  • Needs evidence: Named evidence can still be collected.
  • Unavailable: Required evidence cannot be collected in this run.
  • Waived with evidence: An authorized, scoped exception applies to an established failure.
  • Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Wrap the value in useMemo (objects/arrays) or useCallback (functions) keyed on its real dependencies: const value = useMemo(() => ({ user, theme }), [user, theme]); return <Ctx.Provider value={value}>. If the value never depends on render state, hoist it to a module-level constant instead. Avoid passing inline {}/[]/arrow functions directly to value, since each render creates a new identity and re-renders every consumer. See https://oxc.rs/docs/guide/usage/linter/rules/react/jsx-no-constructed-context-values

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.

Show repository-wide prompt

Fix every confirmed react-doctor/jsx-no-constructed-context-values diagnostic in the current repository.

Required change:

  • Wrap the value in useMemo (objects/arrays) or useCallback (functions) keyed on its real dependencies: const value = useMemo(() => ({ user, theme }), [user, theme]); return <Ctx.Provider value={value}>. If the value never depends on render state, hoist it to a module-level constant instead. Avoid passing inline {}/[]/arrow functions directly to value, since each render creates a new identity and re-renders every consumer. See https://oxc.rs/docs/guide/usage/linter/rules/react/jsx-no-constructed-context-values.

Validation before editing:

Fires on a <X.Provider value={…}> opening element sitting inside a function (a render) when the value expression is constructed fresh each render: an object, array, arrow/function/class expression, new expression, JSX element/fragment, or a conditional/logical whose branches resolve to any of those. Every such provider re-renders all consumers on each parent render because the value gets a new identity. False positive boundary: it only inspects literal construction at the JSX site: an identifier (value={foo}) is never flagged even when foo is an inline {} or an unmemoized useMemo(() => …) with no deps, and spread props (<X.Provider {...rest}>) and member accesses (value={ctx.current}) are likewise not checked, so a confirmed finding is one where the literal sits directly in the attribute.

Constraints:

  • 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.
  • Preserve resource ownership and cleanup. Do not move work into a hotter render or frame path.
  • If syntax proves only a candidate cost, require a relevant trace, bundle report, payload measurement, or metric before editing.
  • Without evidence, record Needs evidence. Compare the same scenario before and after; keep the change only when its target metric improves without regression.
  • Adapt identifiers and framework details instead of copying blindly.
  • Do not disable the rule or suppress matching code.
  • Do not edit code when this condition applies: react-compiler.

Assessment:

  • Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
  • Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
  • A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.

Verification:

  • Run focused tests for the changed behavior.
  • Run React Doctor and confirm this diagnostic no longer appears from changed code.
  • Run an unfiltered scan of the affected scope before claiming no cross-category regression.
  • Report the files changed and any checks you could not run.