Firefox nightly - idx fails to match TypeErrors
See original GitHub issueTypeErrors in Firefox nightly do not pass the undefinedPattern
and nullPattern
tests.
It’s easily reproducible:
- Go to this JSFiddle
- Open the Debugger and check
Pause on exception
- Observe that the error is rethrown while it should be handled on line 65.
Screenshot:
This is due to TypeErrors messages in Firefox nightly being different from regular Firefox, see the same example in regular Firefox:
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Firefox nightly - idx fails to match TypeErrors · Issue #53 · facebook ...
TypeErrors in Firefox nightly do not pass the undefinedPattern and nullPattern tests. It's easily reproducible: Go to this JSFiddle Open the Debugger and ......
Read more >Firefox Nightly Error Collection - Mozilla Support
Firefox Nightly automatically collects and sends Mozilla information about JavaScript errors that occur within the browser itself (not on web pages).
Read more >Websites don't load - troubleshoot and fix error messages
First, let's figure out where the problem is · Open a new tab and check to see if you can load another website...
Read more >Mozilla Firefox Release Notes
761975, extra ")" makes Firefox RPM Nightly build failed ... Add 'localeId' to WebApps registry. 762641, Window matching unreliable for webapprt on Linux....
Read more >[Fetch] "NetworkError when attempting to fetch resource ...
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, ... Fetch requests error out with "TypeError: NetworkError when attempting to fetch ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah well, I think the foundation of this package is a bit broken: it relies on the error messages which are far from being reliable.
We eventually decided not to use it.
In this case, be more precise on the README maybe. Because having this information only in the babel section means if you don’t have babel or don’t want to use it via babel, you won’t read this part.