Why lifecycle hooks run code at key moments in Svelte - Quick Recap

Recall & Review

beginner

What is a lifecycle hook in Svelte?

A lifecycle hook is a special function that runs code at important times during a component's life, like when it starts, updates, or stops.

beginner

Why do we use the onMount lifecycle hook?

onMount runs code right after the component appears on the screen. It's useful for starting tasks like fetching data or setting up timers.

intermediate

What does the beforeUpdate hook do?

beforeUpdate runs code just before the component updates its content on the screen. It helps prepare or check things before the change happens.

intermediate

How does the onDestroy hook help with cleanup?

onDestroy runs code when the component is removed from the screen. It helps stop timers, remove event listeners, or free resources to keep the app fast and clean.

beginner

Why is it important to run code at key moments in a component's life?

Running code at key moments helps the app stay organized, efficient, and responsive. It makes sure things start, update, and stop at the right time, like a well-timed dance.

Which Svelte lifecycle hook runs code right after the component appears on the screen?

A onMount

B beforeUpdate

C afterUpdate

D onDestroy

onMount runs code after the component is added to the page.

What is the main purpose of the onDestroy hook?

A Start timers

B Fetch data

C Clean up resources

D Update the UI

onDestroy helps clean up things like timers and event listeners when the component is removed.

When does the beforeUpdate hook run?

A After the component is removed

B Before the component updates

C When the component mounts

D After the component updates

beforeUpdate runs just before the component changes on the screen.

Why are lifecycle hooks useful in Svelte components?

A To handle user input only

B To write CSS styles

C To create new components

D To run code at important times in the component's life

Lifecycle hooks let you run code exactly when the component starts, updates, or stops.

Which hook would you use to fetch data when a component first appears?

A onMount

B beforeUpdate

C afterUpdate

D onDestroy

onMount is the right place to start tasks like fetching data when the component loads.

Explain why lifecycle hooks are important in Svelte components and give examples of when you might use them.

Think about what happens when a component starts, changes, or stops.

Describe the difference between beforeUpdate and afterUpdate hooks in Svelte.

Consider when you want to prepare for or respond to updates.

Practice

1. What is the main purpose of lifecycle hooks in Svelte components?

easy

A. To handle user input events

B. To style components dynamically

C. To define component props

D. To run code at important moments during a component's life

Solution

1. Step 1: Understand lifecycle hooks

   Lifecycle hooks are special functions that run at specific times in a component's life, like when it appears or disappears.

2. Step 2: Identify their main role

   The main role is to run code at these key moments, such as setup or cleanup tasks.

3. Final Answer:

   To run code at important moments during a component's life -> Option D

4. Quick Check:

   Lifecycle hooks = run code at key moments [OK]

Hint: Lifecycle hooks run code at key moments in component life [OK]

Common Mistakes:

• Thinking lifecycle hooks are for styling
• Confusing hooks with event handlers
• Believing hooks define props

2. Which Svelte lifecycle hook is used to run code right after the component is added to the page?

easy

A. onMount

B. onDestroy

C. beforeUpdate

D. afterUpdate

Solution

1. Step 1: Recall lifecycle hook purposes

   onMount runs code after the component appears on the page, perfect for setup tasks.

2. Step 2: Match hook to timing

   onDestroy runs when component is removed, beforeUpdate and afterUpdate run around updates, not mounting.

3. Final Answer:

   onMount -> Option A

4. Quick Check:

   Code after component appears = onMount [OK]

Hint: onMount runs code after component appears [OK]

Common Mistakes:

• Using onDestroy for setup
• Confusing beforeUpdate with onMount
• Thinking afterUpdate runs on mount

3. Consider this Svelte code:

import { onMount, onDestroy } from 'svelte';

let timer;
onMount(() => {
  timer = setInterval(() => console.log('tick'), 1000);
});
onDestroy(() => {
  clearInterval(timer);
});

What happens when this component is removed from the page?

medium

A. The timer keeps running and logs 'tick' forever

B. An error occurs because clearInterval is missing

C. The timer stops and no more 'tick' logs appear

D. The component reloads automatically

Solution

1. Step 1: Understand onMount and onDestroy usage

   onMount starts a timer that logs 'tick' every second. onDestroy clears that timer when component is removed.

2. Step 2: Predict behavior on removal

   When removed, onDestroy runs and clears the timer, stopping the logs.

3. Final Answer:

   The timer stops and no more 'tick' logs appear -> Option C

4. Quick Check:

   onDestroy clears timer = stops logs [OK]

Hint: onDestroy cleans up timers to stop actions [OK]

Common Mistakes:

• Assuming timer runs forever
• Forgetting to clear timers causes memory leaks
• Thinking component reloads on removal

4. This Svelte code uses lifecycle hooks:

import { onMount } from 'svelte';

onMount(() => {
  console.log('Mounted');
});

onMount(() => {
  console.log('Setup');
});

What is the problem here?

medium

A. Only the first onMount runs, the second is ignored

B. Both onMount hooks run correctly without error

C. Multiple onMount hooks cause a syntax error

D. onMount must be inside a component function

Solution

1. Step 1: Check multiple onMount usage

   Svelte allows multiple onMount calls; all run in order when component mounts.

2. Step 2: Confirm no syntax or scope errors

   Both hooks run and log messages; no syntax error or ignoring occurs.

3. Final Answer:

   Both onMount hooks run correctly without error -> Option B

4. Quick Check:

   Multiple onMount hooks run fine [OK]

Hint: Multiple onMount hooks run in order, no error [OK]

Common Mistakes:

• Thinking multiple hooks cause errors
• Believing only one hook runs
• Assuming onMount must be inside a function

5. You want to fetch data when a Svelte component appears and cancel the fetch if the component is removed before it finishes. Which lifecycle hooks should you use and why?

hard

A. Use onMount to start fetch and onDestroy to cancel it

B. Use beforeUpdate to start fetch and afterUpdate to cancel it

C. Use onDestroy to start fetch and onMount to cancel it

D. Use afterUpdate to start fetch and beforeUpdate to cancel it

Solution

1. Step 1: Identify when to start fetch

   Fetching data should start when component appears, so onMount is the right hook.

2. Step 2: Identify when to cancel fetch

   If component is removed before fetch finishes, onDestroy runs to cancel or clean up the fetch.

3. Final Answer:

   Use onMount to start fetch and onDestroy to cancel it -> Option A

4. Quick Check:

   Start onMount, cancel onDestroy [OK]

Hint: Start fetch onMount, cancel onDestroy for cleanup [OK]

Common Mistakes:

• Using update hooks for fetch start/cancel
• Starting fetch onDestroy (too late)
• Canceling fetch onMount (too early)