react-doctor/ink-use-suspend-terminal
Interactive child process bypasses Ink suspension
- Category: Bugs
- Severity: error
- Source:
oxlint-plugin-react-doctor - Framework: global
- Enabled when: Ink >= 7.1.0
- Tags: ink
- Default: Enabled
Validate the diagnostic
Confirm the reported code matches this rule before you edit it.
Confirm the reported code matches react-doctor/ink-use-suspend-terminal. 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 { useInput } from "ink";
import { spawn } from "node:child_process";
const App = () => {
useInput(() => {
spawn("vim", [], { stdio: "inherit" });
});
return null;
};Corrected pattern
import { useApp, useInput } from "ink";
import { spawn } from "node:child_process";
const App = () => {
const { suspendTerminal } = useApp();
useInput(() => {
suspendTerminal(() => {
spawn("vim", [], { stdio: "inherit" });
});
});
return null;
};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
Reference transformation:Before:react-doctor/ink-use-suspend-terminal diagnostic in the current repository.
Required change:
- Run inherited-TTY child processes inside useApp().suspendTerminal().import { useInput } from "ink";
import { spawn } from "node:child_process";
const App = () => {
useInput(() => {
spawn("vim", [], { stdio: "inherit" });
});
return null;
};import { useApp, useInput } from "ink";
import { spawn } from "node:child_process";
const App = () => {
const { suspendTerminal } = useApp();
useInput(() => {
suspendTerminal(() => {
spawn("vim", [], { stdio: "inherit" });
});
});
return null;
};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:
Ink >= 7.1.0.
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.Related rules
More Bugs rules from the rules reference:
react-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])react-doctor/jotai-tq-use-raw-query-atom: Derive the field once, then subscribe to the derived atom: const dataAtom = atom((get) => get(queryAtom).data)react-doctor/jsx-key: Require a stable key on elements rendered from arrays or iterators so React can reconcile list items correctly.react-doctor/jsx-no-comment-textnodes: Wrap JSX comments in `{/* … */}` so they're parsed as comments, not rendered as literal child text.