Bug: Unexpected debugger statement in DevTools (solved)

[eiamei]

Looks like you forgot about the debugger inside the react_devtools_backend.js.

React dev tools version: 4.8.0

Steps To Reproduce

1. Update (or install) the latest version of devtools
2. Open devtools
3. The code will be stopped on the debugger inside react_devtools_backend.js

The current behavior

If I open devtools with react dev tools extension it will stop every time on debugger inside react_devtools_backend.js

The expected behavior

It doesn't seem like it should be happening 😃

[JakubRimal]

Same here, I've had to disable the extension because of this... 😄

[martinhorsky]

Same for me.

[gaearon]

Looks bad.

[antislash21]

Same here

[Lukortech]

react/packages/react-devtools-shared/src/backend/console.js

Line 173 in 14084be

debugger;

That's the guy you're looking for :D

[gaearon]

Yes, but see the comment above it. :-) It is intentional, but this option should have been off by default.

[przemuh]

As a temporary solution you can "blackbox" script in Chrome Dev Tools:

[gaearon]

You should also be able to go to Components tab, press Settings gear, add checkbox to Break on Warning, then do this again, and remove the checkbox as a temporary workaround.

[gaearon]

I'll keep it open until we cut a release

[eiamei]

Thanks 🙌

[gaearon]

I've submitted a fix to Chrome addons. It should appear there in a few hours. If it doesn't work after updating to 4.8.1, try to clear your local storage (localStorage.clear()).

I can't figure out how to submit it to FF store because something in our process has changed. So @bvaughn will be able to help us out there when he wakes up. :-)

[gaearon]

Here's a step-by-step instruction for how to work around it while the fix is pending review:

1. Press the Settings gear icon in the upper right corner

2. Open the Debugging tab

3. Put the checkmark next to Break on Warnings

4. Remove the checkmark next to Break on Warnings

Now reload the page and you shouldn't be bothered by it.

[gaearon]

Please refrain from "same" comments unless you have something new to say. They are not helpful and obscure the workaround (#19308 (comment)).

[bvaughn]

Update:

• The fix has been published to NPM as 4.81
• The updated extension (with fix) is live for Firefox
• The updated extension is pending for Chrome
• Edge is still providing the previous version 4.7 (but an updated 4.8.1 is also pending for review)

[bvaughn]

We'll keep this issue open until the fix has been deployed on Chrome, but I'm going to lock it to prevent +1 😄

[bvaughn]

4.8.1 is live in Chrome store now too, so I'm going to close this.