Standalone development tool for debugging React applications outside of browser environments
—
Quality
Pending
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Command-line interface for launching the standalone React DevTools application with an Electron-based desktop interface for debugging React applications.
Launches the standalone DevTools application in an Electron window.
react-devtools [project-roots...]Parameters:
project-roots (optional): Array of project root directory paths for "click to open in editor" functionalityUsage Examples:
# Basic usage - launch DevTools
react-devtools
# With project root for editor integration
react-devtools /path/to/my/project
# Multiple project roots
react-devtools /path/to/frontend /path/to/backend
# Global installation
npm install -g react-devtools
react-devtools
# Local installation via npx
npx react-devtoolsThe CLI tool respects the following environment variables:
REACT_DEVTOOLS_PORT=<port>REACT_DEVTOOLS_PORT
Usage Examples:
# Use custom port
REACT_DEVTOOLS_PORT=9090 react-devtools
# Windows
set REACT_DEVTOOLS_PORT=9090 && react-devtoolsThe CLI launches a standalone Electron application with the following features:
When project roots are provided, the DevTools application gains enhanced functionality:
The CLI tool supports opening files in various editors:
codeatomsublvim, nvimemacsThe CLI includes automatic update checking:
# Update with npm
npm update -g react-devtools
# Update with yarn
yarn global upgrade react-devtoolsPort Already in Use
Another instance of DevTools is running.
Only one copy of DevTools can be used at a time.Solution: Close other DevTools instances or use a different port
Connection Timeout
adb reverse tcp:8097 tcp:8097React Native Connection Issues:
react-devtoolsadb reverse tcp:8097 tcp:8097Editor Integration Issues:
Install with Tessl CLI
npx tessl i tessl/npm-react-devtools