AbortController for cancellation in Node.js - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of AbortController in Node.js?

AbortController is used to cancel asynchronous operations like fetch requests or timers before they complete.

beginner

How do you create an AbortController instance and use it to cancel a fetch request?

Create an AbortController instance, pass its signal to fetch, then call abort() on the controller to cancel.

beginner

What property of AbortController is passed to asynchronous functions to listen for cancellation?

The signal property is passed to async functions to detect when an abort is requested.

intermediate

What happens when abort() is called on an AbortController?

It triggers the signal to emit an abort event, causing operations listening to it to stop or throw an error.

intermediate

Can AbortController be reused after calling abort()?

No, once abort() is called, the controller cannot be reset or reused. You must create a new instance for new operations.

Which property of AbortController do you pass to a fetch request to enable cancellation?

A controller

B abort

C signal

D cancel

The signal property is passed to fetch to listen for cancellation.

What method do you call on an AbortController to cancel an operation?

A end()

B stop()

C cancel()

D abort()

abort() triggers cancellation.

After calling abort(), can you reuse the same AbortController instance for another operation?

A No, you must create a new instance

B Yes, but only after calling reset()

C Yes, it resets automatically

D No, but you can call abort() again

Once aborted, the controller cannot be reused; create a new one.

Which event does the signal emit when abort() is called?

A cancel

B abort

C stop

D end

The signal emits an abort event.

What is a common use case for AbortController in Node.js?

A To cancel long-running async tasks like fetch or timers

B To speed up synchronous code

C To handle errors in synchronous functions

D To create new HTTP servers

It is used to cancel asynchronous tasks before they finish.

Explain how you would use AbortController to cancel a fetch request in Node.js.

Think about the steps from creating the controller to stopping the fetch.

Describe what happens internally when abort() is called on an AbortController.

Focus on the signal and event behavior.

Practice

1. What is the main purpose of AbortController in Node.js?

easy

A. To manage file system permissions

B. To create new HTTP servers

C. To cancel ongoing asynchronous operations like fetch requests

D. To handle database connections

Solution

1. Step 1: Understand AbortController's role

   AbortController is designed to stop or cancel asynchronous tasks such as fetch requests.

2. Step 2: Compare with other options

   Creating servers, managing permissions, or handling databases are unrelated to AbortController's purpose.

3. Final Answer:

   To cancel ongoing asynchronous operations like fetch requests -> Option C

4. Quick Check:

   AbortController cancels async tasks = C [OK]

Hint: AbortController is about stopping async tasks quickly [OK]

Common Mistakes:

• Confusing AbortController with server or database management
• Thinking it manages permissions
• Assuming it creates servers

2. Which of the following is the correct way to create an AbortController and get its signal?

easy

A. const signal = new AbortController.signal();

B. const controller = new AbortController; const signal = controller.abort();

C. const controller = AbortController(); const signal = controller.abort;

D. const controller = new AbortController(); const signal = controller.signal;

Solution

1. Step 1: Check correct instantiation syntax

   AbortController must be created with 'new AbortController()' and its signal accessed via 'controller.signal'.

2. Step 2: Identify errors in other options

   const signal = new AbortController.signal(); wrongly calls signal as a constructor. const controller = AbortController(); const signal = controller.abort; misses 'new' and uses 'abort' instead of 'signal'. const controller = new AbortController; const signal = controller.abort(); misses parentheses on 'new AbortController()' and calls 'abort()' instead of accessing 'signal'.

3. Final Answer:

   const controller = new AbortController(); const signal = controller.signal; -> Option D

4. Quick Check:

   Use 'new' and access 'signal' property = B [OK]

Hint: Always use 'new AbortController()' and get 'signal' property [OK]

Common Mistakes:

• Forgetting 'new' keyword
• Calling 'abort' instead of accessing 'signal'
• Treating 'signal' as a constructor

3. What will be the output of this code snippet?

const controller = new AbortController();
const signal = controller.signal;

setTimeout(() => controller.abort(), 100);

signal.addEventListener('abort', () => console.log('Aborted!'));

medium

A. Logs 'Aborted!' after 100 milliseconds

B. Logs 'Aborted!' immediately

C. Throws an error immediately

D. No output, because abort is never called

Solution

1. Step 1: Understand the abort timing

   The controller.abort() is called after 100 milliseconds using setTimeout.

2. Step 2: Check event listener behavior

   The signal listens for 'abort' event and logs 'Aborted!' when triggered.

3. Final Answer:

   Logs 'Aborted!' after 100 milliseconds -> Option A

4. Quick Check:

   Abort triggers event after delay = D [OK]

Hint: Abort triggers event after delay, not immediately [OK]

Common Mistakes:

• Assuming abort happens immediately
• Expecting no output because of async delay
• Thinking it throws error instead of event

4. Identify the error in this code snippet that uses AbortController:

const controller = new AbortController();
const signal = controller.signal;

fetch('https://example.com', { signal });
controller.abort();

signal.addEventListener('abort', () => console.log('Fetch aborted'));

medium

A. Not passing the signal to fetch options

B. Calling abort() before adding the abort event listener

C. Using signal.addEventListener instead of controller.addEventListener

D. Missing async/await for fetch

Solution

1. Step 1: Check event listener timing

   The abort event listener is added after calling controller.abort(), so it misses the event.

2. Step 2: Verify other parts

   The signal is correctly passed to fetch, and signal is the right object to listen on. Async/await is optional here.

3. Final Answer:

   Calling abort() before adding the abort event listener -> Option B

4. Quick Check:

   Add event listener before abort() call = A [OK]

Hint: Add abort listener before calling abort() [OK]

Common Mistakes:

• Adding listener after abort() call
• Listening on controller instead of signal
• Forgetting to pass signal to fetch

5. You want to cancel a fetch request if it takes longer than 200ms. Which code correctly implements this using AbortController?

hard

A. const controller = new AbortController();
setTimeout(() => controller.abort(), 200);
fetch('https://api.com/data', { signal: controller.signal })
.catch(err => { if (err.name === 'AbortError') console.log('Request timed out'); });

B. const controller = new AbortController();
fetch('https://api.com/data', { signal: controller.signal });
setTimeout(() => controller.abort(), 200);
console.log('Request timed out');

C. const controller = new AbortController();
fetch('https://api.com/data');
setTimeout(() => controller.abort(), 200);
.catch(err => console.log('Request timed out'));

D. const controller = new AbortController();
setTimeout(() => controller.abort(), 200);
fetch('https://api.com/data', { signal: controller.abort() })
.catch(err => console.log('Request timed out'));

Solution

1. Step 1: Setup AbortController and timeout

   Create controller, set timeout to call abort after 200ms.

2. Step 2: Pass signal to fetch and handle abort error

   Pass controller.signal to fetch options and catch AbortError to log timeout message.

3. Step 3: Identify errors in other options

   const controller = new AbortController(); fetch('https://api.com/data', { signal: controller.signal }); setTimeout(() => controller.abort(), 200); console.log('Request timed out'); logs timeout immediately, not on abort. const controller = new AbortController(); fetch('https://api.com/data'); setTimeout(() => controller.abort(), 200); .catch(err => console.log('Request timed out')); misses passing signal. const controller = new AbortController(); setTimeout(() => controller.abort(), 200); fetch('https://api.com/data', { signal: controller.abort() }) .catch(err => console.log('Request timed out')); incorrectly calls abort() instead of passing signal.

4. Final Answer:

   const controller = new AbortController(); setTimeout(() => controller.abort(), 200); fetch('https://api.com/data', { signal: controller.signal }) .catch(err => { if (err.name === 'AbortError') console.log('Request timed out'); }); -> Option A

5. Quick Check:

   Pass signal, abort after delay, catch AbortError = A [OK]

Hint: Pass controller.signal to fetch and abort after timeout [OK]

Common Mistakes:

• Calling abort() instead of passing signal
• Logging timeout before abort happens
• Not passing signal to fetch