Safely Landing Your Code: Mastering the Finally Block in JavaScript

Welcome back! After exploring the try and catch blocks in JavaScript, we're now moving on to the finally block, a companion of the try and catch blocks, performing the necessary cleanup. Today, we'll explore its application.

The finally block is a section of code that always executes after the try and catch blocks, running irrespective of whether an exception occurred. This block executes no matter if the exception has happened or not. Curious? Let's take a look:

try {
  // run some code
} catch (error) {
  // handle the error
} finally {
  // always run this code
}

This is the basic structure of the try/catch/finally block. See - no matter what's inside try and catch, the content of the finally block will be executed after them, allowing you to proceed with some cleanup or post-actions!

Let's look into finally applications in more detail.

The finally block handles activities that are either risky or not after the try and catch blocks have been executed. Whether your try block throws an exception or not, it doesn't matter — the finally block ensures necessary tasks are completed. For example, when interacting with a database, you must close the connection. This is done with finally:

let dbConnection;

try {
  dbConnection = openDatabase();  // try to open a connection
  // try some operations
} catch (error) {
  console.error("An error occurred!", error); // catch and handle exceptions
} finally {
  dbConnection.close(); // always close the connection
}

While this example might not be something you face right away, it's important to understand the appliance of the finally block in real life.

Let's dive into action. In this example, the finally block executes and logs "Finally!" to the console, regardless of the exception:

try {
  console.log("In the try block");
  throw new Error("Oops, an error!"); // This causes an exception
} catch (error) {
  console.log("In the catch block");
} finally {
  console.log("Finally!"); // This gets printed always
}
// Prints:
// In the try block
// In the catch block
// Finally!

Even in the absence of exceptions, the finally block still runs:

try {
  console.log("In the try block");
} catch (error) {
  console.log("In the catch block");
} finally {
  console.log("Finally!"); // This still gets printed
}
// Prints:
// In the try block
// Finally!