Finally block in Javascript

Introduction

The finally block runs code after try and catch, no matter what happens. It helps clean up or finish tasks.

You want to close a file or connection after trying to read it.

You want to stop a loading spinner after a task finishes, whether it worked or failed.

You want to reset variables or states after an operation.

You want to log that a process ended, no matter if it succeeded or threw an error.

Syntax

Javascript

try {
  // code that might throw an error
} catch (error) {
  // code to handle the error
} finally {
  // code that runs always
}

The finally block runs after try and catch, even if there is no error.

If you return inside try or catch, finally still runs before the function returns.

Examples

This shows all blocks. Since no error happens, catch is skipped but finally runs.

Javascript

try {
  console.log('Try block runs');
} catch (e) {
  console.log('Catch block runs');
} finally {
  console.log('Finally block runs');
}

Here, an error is thrown and caught. The finally block runs after catch.

Javascript

try {
  throw new Error('Oops');
} catch (e) {
  console.log('Caught:', e.message);
} finally {
  console.log('Always runs');
}

Even with a return in try, finally runs before the function returns.

Javascript

function test() {
  try {
    return 'From try';
  } finally {
    console.log('Finally runs before return');
  }
}
console.log(test());

Sample Program

This program tries to read data but throws an error. The error is caught and logged. The finally block cleans up resources no matter what.

Javascript

function readData() {
  try {
    console.log('Reading data...');
    throw new Error('Failed to read');
  } catch (error) {
    console.log('Error:', error.message);
  } finally {
    console.log('Cleaning up resources');
  }
}
readData();

Important Notes

The finally block is useful for cleanup tasks like closing files or stopping timers.

If the finally block itself throws an error, that error will replace any previous error or return value.

Summary

The finally block always runs after try and catch.

Use it to run code that must happen no matter what, like cleanup.

It runs even if there is a return or error inside try or catch.

Practice

1.

What is the main purpose of the finally block in JavaScript?

easy

A. To define variables used in try block

B. To run code that always executes after try and catch blocks

C. To catch errors thrown in the try block

D. To skip the catch block if no error occurs

Solution

1. Step 1: Understand try-catch-finally structure

   The try block runs code that might throw errors, catch handles those errors.

2. Step 2: Role of finally block

   The finally block runs code after try and catch, no matter if an error occurred or not.

3. Final Answer:

   To run code that always executes after try and catch blocks -> Option B

4. Quick Check:

   finally always runs = C [OK]

Hint: finally always runs after try/catch, no matter what [OK]

Common Mistakes:

• Thinking finally only runs if there is an error
• Confusing catch and finally blocks
• Believing finally can catch errors

2.

Which of the following is the correct syntax to add a finally block after a try and catch block?

try {
  // code
} catch (e) {
  // handle error
} ??? {
  // cleanup code
}

easy

A. cleanup

B. final

C. finally

D. end

Solution

1. Step 1: Recall JavaScript error handling syntax

   The correct keyword after catch is 'finally' to run code always.

2. Step 2: Check options for correct keyword

   Only 'finally' is valid JavaScript syntax here.

3. Final Answer:

   finally -> Option C

4. Quick Check:

   finally keyword syntax = D [OK]

Hint: finally is the exact keyword after catch for cleanup [OK]

Common Mistakes:

• Using 'final' or 'end' instead of 'finally'
• Omitting the finally block keyword
• Placing finally before catch

3.

What will be the output of this code?

function test() {
  try {
    console.log('Try block');
    return 'Return from try';
  } catch (e) {
    console.log('Catch block');
  } finally {
    console.log('Finally block');
  }
}
console.log(test());

medium

A. Finally block\nReturn from try

B. Try block\nCatch block\nFinally block\nReturn from try

C. Try block\nReturn from try

D. Try block\nFinally block\nReturn from try

Solution

1. Step 1: Trace the try block execution

   It logs 'Try block' and then hits return 'Return from try'.

2. Step 2: Understand finally runs after return

   Even after return, finally runs and logs 'Finally block'. Then function returns.

3. Final Answer:

   Try block\nFinally block\nReturn from try -> Option D

4. Quick Check:

   finally runs after return = A [OK]

Hint: finally runs even after return in try [OK]

Common Mistakes:

• Thinking finally does not run after return
• Expecting catch block to run without error
• Missing the order of console logs

4.

Find the error in this code snippet:

try {
  throw new Error('Oops');
} catch {
  console.log('Caught error');
} finally {
  console.log('Cleanup');
}

medium

A. No error, code runs fine

B. finally block cannot be used without catch parameter

C. throw statement is incorrect

D. Missing error parameter in catch block

Solution

1. Step 1: Check catch block syntax

   Optional catch binding (ES2019+) allows catch {} without parameter. Valid in modern JavaScript.

2. Step 2: Verify execution

   Throws error, catch logs 'Caught error', finally logs 'Cleanup'. No errors.

3. Final Answer:

   No error, code runs fine -> Option A

4. Quick Check:

   catch {} valid = D [OK]

Hint: catch {} valid in modern JS with optional binding [OK]

Common Mistakes:

• Thinking catch always requires parameter
• Believing syntax error without catch param
• Confusing with pre-ES2019 JS

5.

Consider this code:

let result = '';
function test() {
  try {
    result += 'Try';
    throw new Error('Error!');
  } catch (e) {
    result += 'Catch';
    return result;
  } finally {
    result += 'Finally';
  }
}
test();
console.log(result);

What will be printed to the console?

hard

A. TryCatchFinally

B. TryCatch

C. TryFinally

D. Try

Solution

1. Step 1: Trace try block execution

   result becomes 'Try', then error is thrown.

2. Step 2: Catch block runs and appends 'Catch', then returns result ('TryCatch')

   Before returning, finally runs and appends 'Finally' to result.

3. Step 3: Check console.log output

   console.log prints result after finally appended, so 'TryCatchFinally'.

4. Final Answer:

   TryCatchFinally -> Option A

5. Quick Check:

   finally runs before return completes = B [OK]

Hint: finally runs before return completes, modifies variables [OK]

Common Mistakes:

• Assuming return stops finally from running
• Expecting console.log to print before finally modifies result
• Ignoring that finally runs even after return