Deno•3y ago

Why isn't this error caught?

Basic code example:

try {
  Deno.remove("fakefile");
} catch (err) {
  console.log("File doesn't exist...");
}

console.log("That file didn't exist");

try {
  Deno.remove("fakefile");
} catch (err) {
  console.log("File doesn't exist...");
}

console.log("That file didn't exist");

The output when you run this is the following:

❯ deno run -A delete.js
That file didn't exist
error: Uncaught (in promise) NotFound: No such file or directory (os error 2), remove 'fakefile'
    at async Object.remove (ext:deno_fs/30_fs.js:175:3)

❯ deno run -A delete.js
That file didn't exist
error: Uncaught (in promise) NotFound: No such file or directory (os error 2), remove 'fakefile'
    at async Object.remove (ext:deno_fs/30_fs.js:175:3)

So the code within the

catch

catch

statement isn't running, but the code after the catch statement is executed. And yet the program crashes due to an uncaught error.

Captain 𝗕𝗘𝗘𝗙🥩OP•3/22/23, 8:34 PM

Interesting, I'll give this a try. Thanks!

Doctor 🤖•3/22/23, 10:51 PM

You don’t need to handle it like this. You just need to await it within the try catch.

Doctor 🤖•3/22/23, 10:51 PM

Not awaiting it will let the try catch continue down and out, not catching any errors that the promise may throw.

Doctor 🤖•3/22/23, 10:53 PM

Doctor 🤖•3/22/23, 10:55 PM

Basically where the promise is being resolved is where the errors from the promise will be thrown and caught.