Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

console.log commands are not shown their code line locations

See original GitHub issue

After 0.61.x releases on the debug mode console.log commands are not showing their code line locations. They always shown at ... Project Directioy ...\projectName\node_modules\react-native\Libraries\Core\setUpDeveloperTools.js:73 directory.

For example; Before update: 1_Ot8O3BcmnRF_JkeerVYWfA

After update: t1 (1)

Is this a bug? If it’s not previous version was way more useful for variable, data or etc… tracking.

Versions:

    "react": "16.9.0",
    "react-native": "0.61.1"

Environment: [skip envinfo]

Issue Analytics

State:
Created 4 years ago
Reactions:19
Comments:36 (16 by maintainers)

Top GitHub Comments

7reactions

rickhanloniicommented, Oct 16, 2019

This is fixed by https://github.com/facebook/react-native/pull/26883

That diff will revert this back to showing “YellowBox.js”:

This will stay the case until Chrome exposes a way for us to ignore our wrapping frame (see here).

Until then, if you want to see the true frame, you can blackbox YellowBox.js (or any script) and Chrome will know to skip that frame:

Note: The regexes to use are /YellowBox\.js$ and /setUpDeveloperTools\.js$

Note: Notice that App.js is referenced here instead of YellowBox.js

You can read more about Chrome Blackboxing here

7reactions

IceDev-xyzcommented, Oct 13, 2019

I also use Chrome Debugger tools, It feels simpler… if this decision can be discussed, count my vote for allowing to see logs like before without having to install React DevTools.