err-saga.js causes problems when syntax errors are caught
See original GitHub issueWhen a syntax error is caught, err-saga.js
gets as far as line 5 and stops all processes.
There is a syntax error message in the dev console
There is no error toast
I can’t see anything in ~ /client/commonFramwork/
working eg. code-storage
, detect-unsafe-code-stream
, display-test-results` etc…
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Can syntax errors be caught in JavaScript? - Stack Overflow
You cannot use try-catch blocks to handle syntax errors as they are thrown while the code is being parsed and not while it's...
Read more >SyntaxError - JavaScript - MDN Web Docs
The SyntaxError object represents an error when trying to interpret syntactically invalid code. It is thrown when the JavaScript engine encounters tokens or ......
Read more >How to Handle the Syntax Error in Javascript - Rollbar
The Javascript SyntaxError is caused by the incorrect use of a pre-defined syntax. Syntax errors are detected while interpreting or parsing ...
Read more >JavaScript Syntax Errors and How to Prevent Them - Meticulous
The following are some examples of syntax errors that commonly cause trouble for developers. Missing or Unmatched Quotation Marks. Quotation ...
Read more >JavaScript Beginners - Know How To Solve Your Syntax Errors
In this tutorial, we're going to take a look at syntax errors in JavaScript and how to solve syntax errors in JavaScript if...
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
I’d like to take on this bug.
I have just pulled the latest
staging
and tried this out again.Running tests with an unfinished function declaration in the code causes the error toast, but nothing happens after that.
Output remains at
// running test
The test-suite switches and remains in its initial state
There is no error message in
output
It looks like
throwers()
is throwing the Error object correctly,but this error never makes it to the console. In it’s place is an Error thrown by
Parser.pp.raise
:This is
parser.pp.raise
:This part of webpack is overriding the Error object from
throwers