Why lifecycle hooks run code at key moments in Svelte

Introduction

Lifecycle hooks let you run code exactly when your component starts, updates, or ends. This helps you control what happens at important times.

When you want to fetch data right after a component appears on the screen.

When you need to clean up timers or event listeners before a component disappears.

When you want to react to changes in component data or props.

When you want to set up animations when a component is created.

When you want to log or track component behavior during its life.

Syntax

Svelte

import { onMount, beforeUpdate, afterUpdate, onDestroy } from 'svelte';

onMount(() => {
  // code to run when component is added to the page
});

beforeUpdate(() => {
  // code to run before the component updates
});

afterUpdate(() => {
  // code to run after the component updates
});

onDestroy(() => {
  // code to run when the component is removed
});

Each hook runs at a specific time in the component's life.

Use onMount for setup, onDestroy for cleanup.

Examples

This runs code once when the component appears.

Svelte

import { onMount } from 'svelte';

onMount(() => {
  console.log('Component is ready!');
});

This runs code once just before the component is removed.

Svelte

import { onDestroy } from 'svelte';

onDestroy(() => {
  console.log('Component is leaving.');
});

These run code before and after the component updates.

Svelte

import { beforeUpdate, afterUpdate } from 'svelte';

beforeUpdate(() => {
  console.log('About to update');
});

afterUpdate(() => {
  console.log('Just updated');
});

Sample Program

This component starts a timer when it appears and increases a count every second. When the component is removed, it stops the timer to avoid problems.

Svelte

<script>
  import { onMount, onDestroy } from 'svelte';

  let timer;
  let count = 0;

  onMount(() => {
    console.log('Component mounted');
    timer = setInterval(() => {
      count += 1;
      console.log(`Count is now ${count}`);
    }, 1000);
  });

  onDestroy(() => {
    clearInterval(timer);
    console.log('Component destroyed and timer cleared');
  });
</script>

<p>Count: {count}</p>

Important Notes

Always clean up resources like timers or event listeners in onDestroy to avoid memory leaks.

Lifecycle hooks help keep your component's behavior organized and predictable.

Summary

Lifecycle hooks run code at key moments in a component's life.

Use onMount to start things and onDestroy to clean up.

Hooks like beforeUpdate and afterUpdate help react to changes.

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)