react-doctor/ink-suspense-requires-concurrent
Retired: Ink Suspense rendering mode
- Category: Bugs
- Severity: error
- Source:
oxlint-plugin-react-doctor - Framework: global
- Enabled when: Ink >= 6.7.0
- Tags: ink
- Status: Retired
- Default: Disabled until configured
Validate the diagnostic
Confirm the reported code matches this rule before you edit it.
This rule is retired and disabled by default. Do not change application code. If it still appears, check the installed React Doctor version and rule configuration.
How to fix
This rule is retired, so no code change is required.
Copyable fix prompt
Copy this self-contained prompt into your coding agent after you confirm the diagnostic.
Resolve any stale
react-doctor/ink-suspense-requires-concurrent report without changing application code.
No change is required; Ink can render Suspense fallbacks without concurrency.
Checks:
- Confirm the installed React Doctor version.
- Update React Doctor if the project uses an older version.
- Remove configuration that explicitly enables this retired rule.
- Run React Doctor and confirm the report no longer appears.
Report the version, configuration, and command you checked.Related rules
More Bugs rules from the rules reference:
react-doctor/ink-use-reactive-window-size: Terminal dimensions read non-reactivelyreact-doctor/ink-use-string-width-for-cursor: String length used as terminal column widthreact-doctor/ink-use-suspend-terminal: Interactive child process bypasses Ink suspensionreact-doctor/jotai-derived-atom-returns-fresh-object: Split the derivation into per-field primitive derived atoms, or wrap with selectAtom(source, fn, shallow) from jotai/utils when a wrapper object is required.react-doctor/jotai-select-atom-in-render-body: Lift selectAtom to module scope, or wrap it: const a = useMemo(() => selectAtom(base, fn), [deps])