-
Notifications
You must be signed in to change notification settings - Fork 46.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix a bug in console.log with non-string args (#24546)
- Loading branch information
1 parent
34da5aa
commit 852f10b
Showing
2 changed files
with
4 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
852f10b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this PR broke things: https://stackoverflow.com/questions/72216782/uncaught-typeerror-inputargs0-match-is-not-a-function
@mondaychen I started getting errors when doing:
in next.js
It's also weird that the Chrome Extension isn't listed in the Chrome Extension Store now...
852f10b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, maybe this fixes things and this commit isn't released. Your PR says it should fix the issue I'm finding. But it's very odd that the Chrome Store doesn't have the extension anymore..
852f10b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @vpontis this is because it (usually) take a day for each version of an extension to be reviewed before it can be published on chrome web store. Please refer to #24543 and #24549 for details. This issue is resolved now.