-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working in chrome 83 #80
Comments
It appears to be an issue of Node still spitting our non agnostic debugging URLS. And the new version of Chrome removing some fallback code. See https://chromium-review.googlesource.com/c/chromium/src/+/1582881 I've actually implemented and pushed a fix to GitHub. I will shortly push to the Chrome Web Store however there's no telling how long it will take for that to go thru. |
For those so inclined who would rather not wait I've pushed the file here as well: |
edge: https://microsoftedge.microsoft.com/addons/detail/injfmegnapmoakbmnmnecjabigpdjeme So I published the update to both Microsoft and Google. In the event Google in fact takes
I would suggest trying Microsoft Edge as I've found things go through the pipeline much faster with them. |
Thank you so much! Increadible! Perfect! |
WOW, I take it back! Kudos @dotproto and team for the swift approval! |
Today I update my chrome to 83. And now this extension is broken... After write node --inspect --inspect-brk - I get many, very many tabs in chrome... New tab is opening every half second until stop terminal. The same behavior in canary (version 85)
The text was updated successfully, but these errors were encountered: