Handle console.error & console.warn calls

[barbushin]

Handle console.error & console.warn calls

[barbushin]

Great idea! I just tested it, and I see that it's very easy to override standard console.* functions. I'll implement it soon, when I have some free time.

[jrnail23]

@barbushin, thanks for the quick reply -- that feature would be really great for me and my team, as we test our React apps.
React writes warnings & errors to the console when you violate certain design/coding rules, and this would be a great way to make those problems more visible for us. 😄

[barbushin]

I deployed v2.1.26 in Google WebStore. It's going to be reviewed by WebStore team and published in about 1 hour. Then it will take few hours before your Chrome will download new version. You can use chrome://extensions/ to force updating to new version.

Please let me know if it works fine. Thanks!

[jrnail23]

@barbushin, dude, you freaking rock. 💯

[dsherret]

This caused a lot of issues! stack[3] does not always match the regex in this code. For example, there is no parenthesis in this stack[3]:

"    at https://some-website-goes-here.net/Scripts/FloatingPanel.js:10:10"

When this fails, it throws an error that halts the execution of any code that uses console.warn or console.error. Websites like Jira are barely usable with this extension enabled.

I would highly suggest being a bit more defensive (ex. assume callSrc could be null) and not halt execution of code that uses console.warn/console.error when there is an error in this extension. I bet a lot of people using this extension are confused about why websites aren't working today.

[barbushin]

@dsherret But it's already fixed in fe2be66 Isn't it?

[barbushin]

@dsherret David, you was right. There was some another case with undefined index error. I fixed it in last commit and deployed in WebStore. Looks good for you?

[dsherret]

@barbushin yup, everything's working fine now. Thanks!