Vscode: Node v8.5.0 breaks the "uncaught exception" setting

Created on 18 Sep 2017  路  4Comments  路  Source: microsoft/vscode

  • VSCode Version: 1.17.0-insider (b0c0634)
  • OS Version: MacOS 10.13 Beta (17A362a)
  • Node Version: 8.5.0

Using the same sample code from #1746

function failingFunc() {
  return (undefined as any).nope();
}

let promise = new Promise((resolve, reject) => {
 resolve(failingFunc());
});

promise.then(v => {}).catch((e: Error) => {
  console.log(e.message);
});

"Uncaught exceptions" is disabled, however it keeps breaking, regardless if it checked or unchecked.

screen shot 2017-09-18 at 2 39 48 pm

Reproduces without extensions: Yes

debug upstream

Most helpful comment

You can workaround it in VS Code with

"skipFiles": [ "<node_internals>/**" ]

in your launch config

All 4 comments

I was able to confirm this in the stable version of VSCode as well. I checked whether node was the cause and it looks like it is. Switching to node v8.4.0 no longer has this issue.

I can repro as well, with something as simple as

console.log('before');
Promise.reject(new Error('error'))

This is a Node bug, I filed https://github.com/nodejs/node/issues/15464

You can workaround it in VS Code with

"skipFiles": [ "<node_internals>/**" ]

in your launch config

The fix for this landed in be2a5b3 and will be released in Node v8.7.

The corresponding nodejs/#15464 is closed, so probably safe to close this too? Just wanted to help clean up 馃憤

Was this page helpful?
0 / 5 - 0 ratings

Related issues

VitorLuizC picture VitorLuizC  路  3Comments

v-pavanp picture v-pavanp  路  3Comments

mrkiley picture mrkiley  路  3Comments

curtw picture curtw  路  3Comments

biij5698 picture biij5698  路  3Comments