Skip to content

Bug: react-devtools prints too many logs of WS failed #20095

@Jack-Works

Description

@Jack-Works

React version: Not related

The current behavior

We're following this to set up react-devtools.

If your app is inside an iframe, a Chrome extension, React Native, or in another unusual environment, try the standalone version instead. Chrome apps are currently not inspectable.

The standalone version works well, but if the standalone version is not started, react-devtools will try to connect ws://localhost:8097/ and prints too many logs.

image

The expected behavior

I hope react-devtools can only print 1 error message if it is not connected to the standalone version.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions