You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Conclusion: there seems to be literally no way to execute some JavaScript code without promise rejection errors bubbling all the way up to the top of the execution context (window). And when they get to the top, there seems to be no way to tell where they came from.
Is it possible for you to tag either all user created promises or all app code promises? (By tag I literally mean `promise.came_from_known_place = true`) You can access the original promise from the unhandled rejection event
I can't tag user promises, but I could theoretically tag all of ours. But that would mean permanently excising all async/await from our code. And we'd have to somehow force our special promises into every promise-using library that we use. So maybe possible but very difficult.
Wouldn't modifying the prototype ctor of the browser's Promise automatically force it onto all the libraries?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
