mirror of
https://github.com/zebrajr/react.git
synced 2026-01-15 12:15:22 +00:00
0a7dc1b1c7
## Summary This PR attempts to make running the React DevTools a little friendlier in projects that are not completely React. At the moment, running the DevTools with `npx react-devtools` will default to the port to use the `PORT` env variable otherwise it'll fall back to `8097`. `PORT` is a common env variable, so we can get into this strange situation where the a Rails server (eg Puma) is using `PORT`, and then the React DevTools attempts to boot using the same `PORT`. This PR introduces a dedicated env variable, `REACT_DEVTOOLS_PORT` to assist in this scenario. ## How did you test this change? I'm using fish shell, so I did the following, please let me know if there's a better way: ```sh cd packages/react-devtools set -x PORT 1000 set -x REACT_DEVTOOLS_PORT 2000 node bin.js ``` We can see in the UI that it's listening on `2000`. Without this PR, it'd listen on `1000`: 
146 lines
8.1 KiB
Markdown
146 lines
8.1 KiB
Markdown
# `react-devtools`
|
||
|
||
This package can be used to debug non-browser-based React applications (e.g. React Native, mobile browser or embedded webview, Safari).
|
||
|
||
|
||
|
||
## Installation
|
||
Install the `react-devtools` package. Because this is a development tool, a global install is often the most convenient:
|
||
```sh
|
||
# Yarn
|
||
yarn global add react-devtools
|
||
|
||
# NPM
|
||
npm install -g react-devtools
|
||
```
|
||
|
||
If you prefer to avoid global installations, you can add `react-devtools` as a project dependency. With Yarn, you can do this by running:
|
||
```sh
|
||
yarn add --dev react-devtools
|
||
```
|
||
|
||
With NPM you can just use [NPX](https://www.npmjs.com/package/npx):
|
||
```sh
|
||
npx react-devtools
|
||
```
|
||
|
||
## Usage with React Native
|
||
Run `react-devtools` from the terminal to launch the standalone DevTools app:
|
||
```sh
|
||
react-devtools
|
||
```
|
||
|
||
If you're not using a local simulator, you'll also need to forward ports used by React DevTools:
|
||
```sh
|
||
adb reverse tcp:8097 tcp:8097
|
||
```
|
||
|
||
If you're using React Native 0.43 or higher, it should connect to your simulator within a few seconds. (If this doesn't happen automatically, try reloading the React Native app.)
|
||
|
||
### Integration with React Native Inspector
|
||
|
||
You can open the [in-app developer menu](https://reactnative.dev/docs/debugging#accessing-the-in-app-developer-menu) and choose "Show Inspector". It will bring up an overlay that lets you tap on any UI element and see information about it:
|
||
|
||
|
||
|
||
However, when `react-devtools` is running, Inspector will enter a special collapsed mode, and instead use the DevTools as primary UI. In this mode, clicking on something in the simulator will bring up the relevant components in the DevTools:
|
||
|
||
|
||
|
||
|
||
You can choose "Hide Inspector" in the same menu to exit this mode.
|
||
|
||
### Inspecting Component Instances
|
||
|
||
When debugging JavaScript in Chrome, you can inspect the props and state of the React components in the browser console.
|
||
|
||
First, follow the [instructions for debugging in Chrome](https://reactnative.dev/docs/debugging#chrome-developer-tools) to open the Chrome console.
|
||
|
||
Make sure that the dropdown in the top left corner of the Chrome console says `debuggerWorker.js`. **This step is essential.**
|
||
|
||
Then select a React component in React DevTools. There is a search box at the top that helps you find one by name. As soon as you select it, it will be available as `$r` in the Chrome console, letting you inspect its props, state, and instance properties.
|
||
|
||
|
||
|
||
|
||
## Usage with React DOM
|
||
|
||
The standalone shell can also be useful with React DOM (e.g. to debug apps in Safari or inside of an iframe).
|
||
|
||
Run `react-devtools` from the terminal to launch the standalone DevTools app:
|
||
```sh
|
||
react-devtools
|
||
```
|
||
|
||
Add `<script src="http://localhost:8097"></script>` as the very first `<script>` tag in the `<head>` of your page when developing:
|
||
|
||
```html
|
||
<!doctype html>
|
||
<html lang="en">
|
||
<head>
|
||
<script src="http://localhost:8097"></script>
|
||
```
|
||
|
||
This will ensure the developer tools are connected. **Don’t forget to remove it before deploying to production!**
|
||
|
||
>If you install `react-devtools` as a project dependency, you may also replace the `<script>` suggested above with a JavaScript import (`import 'react-devtools'`). It is important that this import comes before any other imports in your app (especially before `react-dom`). Make sure to remove the import before deploying to production, as it carries a large DevTools client with it. If you use Webpack and have control over its configuration, you could alternatively add `'react-devtools'` as the first item in the `entry` array of the development-only configuration, and then you wouldn’t need to deal either with `<script>` tags or `import` statements.
|
||
|
||
## Advanced
|
||
|
||
By default DevTools listen to port `8097` on `localhost`. The port can be modified by setting the `REACT_DEVTOOLS_PORT` environment variable. If you need to further customize host, port, or other settings, see the `react-devtools-core` package instead.
|
||
|
||
## FAQ
|
||
|
||
### The React Tab Doesn't Show Up
|
||
|
||
**If you are running your app from a local `file://` URL**, don't forget to check "Allow access to file URLs" on the Chrome Extensions settings page. You can find it by opening Settings > Extensions:
|
||
|
||
|
||
|
||
Or you could develop with a local HTTP server like [`serve`](https://www.npmjs.com/package/serve).
|
||
|
||
**The React tab won't show up if the site doesn't use React**, or if React can't communicate with the devtools. When the page loads, the devtools sets a global named `__REACT_DEVTOOLS_GLOBAL_HOOK__`, then React communicates with that hook during initialization. You can test this on the [React website](https://reactjs.org/) or by inspecting [Facebook](https://www.facebook.com/).
|
||
|
||
**If your app is inside of CodePen**, make sure you are registered. Then press Fork (if it's not your pen), and then choose Change View > Debug. The Debug view is inspectable with DevTools because it doesn't use an iframe.
|
||
|
||
**If your app is inside an iframe, a Chrome extension, React Native, or in another unusual environment**, try [the standalone version instead](https://github.com/facebook/react/tree/main/packages/react-devtools). Chrome apps are currently not inspectable.
|
||
|
||
**If your Components tab is empty, refer to "The React tab shows no components" section below**.
|
||
|
||
**If you still have issues** please [report them](https://github.com/facebook/react/issues/new?labels=Component:%20Developer%20Tools). Don't forget to specify your OS, browser version, extension version, and the exact instructions to reproduce the issue with a screenshot.
|
||
|
||
### The React tab shows no components
|
||
|
||
#### The Issue with Chrome v101 and earlier
|
||
As we migrate to a Chrome Extension Manifest V3, we start to use a new method to hook the DevTools with the inspected page. This new method is more secure, but relies on a new API that's only supported in Chrome v102+. For Chrome v101 or earlier, we use a fallback method, which can cause malfunctions (e.g. failure to load React Elements in the Components tab) if the JS resources on your page is loaded from cache. Please upgrade to Chrome v102+ to avoid this issue.
|
||
|
||
#### Service Worker malfunction
|
||
Go to chrome://extensions. If you see "service worker (inactive)" in the React Developer Tools extension, try disabling and re-enabling the extension. This will restart the service worker. Then go to the page you want to inspect, close the DevTools, and reload the page. Open the DevTools again and the React components tab should be working.
|
||
|
||
## Local development
|
||
The standalone DevTools app can be built and tested from source following the instructions below.
|
||
|
||
### Prerequisite steps
|
||
DevTools depends on local versions of several NPM packages<sup>1</sup> also in this workspace. You'll need to either build or download those packages first.
|
||
|
||
<sup>1</sup> Note that at this time, an _experimental_ build is required because DevTools depends on the `createRoot` API.
|
||
|
||
#### Build from source
|
||
To build dependencies from source, run the following command from the root of the repository:
|
||
```sh
|
||
yarn build-for-devtools
|
||
```
|
||
#### Download from CI
|
||
To use the latest build from CI, run the following command from the root of the repository:
|
||
```sh
|
||
./scripts/release/download-experimental-build.js
|
||
```
|
||
### Build steps
|
||
You can test the standalone DevTools by running the following:
|
||
|
||
* **First, complete the prerequisite steps above! If you don't do it, none of the steps below will work.**
|
||
* Then, run `yarn start:backend` and `yarn start:standalone` in `packages/react-devtools-core`
|
||
* Run `yarn start` in `packages/react-devtools`
|
||
* Refresh the app after it has recompiled a change
|
||
* For React Native, copy `react-devtools-core` to its `node_modules` to test your changes.
|