Unsupported syntax "catch { }"
See original GitHub issuenpm build , use _jsdom@16.0.0@jsdom , build error
} catch {
^
SyntaxError: Unexpected token {
at createScript
https://github.com/jsdom/jsdom/commit/d2ae947c60297a8ec404b4adbd78267bedd439f4?diff=split
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (6 by maintainers)
Top Results From Across the Web
Error handling, "try...catch" - The Modern JavaScript Tutorial
The “try…catch” syntax · First, the code in try {...} is executed. · If there were no errors, then catch (err) is ignored:...
Read more >Catch Syntax error in JavaScript for ES6 not supported browsers
I have code like this: window.onerror = function(message) { message += '. Your browser may not support ES6.'; ...
Read more >8. Errors and Exceptions — Python 3.11.1 documentation
Syntax errors, also known as parsing errors, are perhaps the most common kind of complaint you get while you are still learning Python:....
Read more >Control flow and error handling - JavaScript - MDN Web Docs
The try...catch statement marks a block of statements to try, and specifies one or more responses should an exception be thrown.
Read more >4 Errors and Exception Handling
This section describes how to trap predefined TimesTen errors or ... uses Oracle Database syntax or built-in procedures that are not supported by...
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 Free
Top 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
jsdom@16
requiresnode >= 10
, if you have the same issue, please update node to version 10. Closing this issue as it is not relevant to babel.@carlosesh If you have a repository that reproduces the problem I would be happy to look at it.
Is it possible that you have two different node versions installed?