beforeUpdate and afterUpdate in Svelte - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

Understanding beforeUpdate and afterUpdate execution order

Given the following Svelte component, what will be the order of console logs when the button is clicked once?

Svelte

  <script>
    import { beforeUpdate, afterUpdate } from 'svelte';
    let count = 0;

    beforeUpdate(() => {
      console.log('Before update:', count);
    });

    afterUpdate(() => {
      console.log('After update:', count);
    });

    function increment() {
      count += 1;
    }
  </script>

  <button on:click={increment}>Increment</button>
  <p>{count}</p>

A 1,2

B 2,1

C 1

D 2

💡 Hint

Remember that beforeUpdate runs before the DOM updates and afterUpdate runs after.

When the button is clicked, count changes from 0 to 1.

beforeUpdate runs before the DOM reflects this change, so it logs the old value 0.

afterUpdate runs after the DOM updates, so it logs the new value 1.

❓ state_output

intermediate

What is the value of message after update?

Consider this Svelte component. What will be the final value of message after the button is clicked once?

Svelte

  <script>
    import { beforeUpdate, afterUpdate } from 'svelte';
    let message = 'start';

    beforeUpdate(() => {
      message = 'before';
    });

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

    function change() {
      message = 'changed';
    }
  </script>

  <button on:click={change}>Change</button>
  <p>{message}</p>

A "after"

B "before"

C "changed"

D "start"

💡 Hint

Think about the order of lifecycle hooks and how they modify message.

Clicking the button sets message to 'changed'.

Then beforeUpdate runs and sets it to 'before'.

After the DOM updates, afterUpdate runs and logs.

The final displayed value is 'before'.

📝 Syntax

advanced

Identify the syntax error in lifecycle hook usage

Which option contains a syntax error in using beforeUpdate or afterUpdate in Svelte?

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

B afterUpdate(() => console.log('update'));

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

D afterUpdate(() => { console.log('update'); });

💡 Hint

Check the parentheses and arrow function syntax carefully.

Option A uses curly braces instead of parentheses to call beforeUpdate, which is invalid syntax.

All other options correctly call the lifecycle hooks with arrow functions.

🔧 Debug

advanced

Why does afterUpdate cause an infinite loop here?

Examine this Svelte code snippet. Why does it cause an infinite update loop?

Svelte

  <script>
    import { afterUpdate } from 'svelte';
    let count = 0;

    afterUpdate(() => {
      count += 1;
    });
  </script>

  <p>{count}</p>

A Because <code>afterUpdate</code> is not imported correctly.

B Because <code>count</code> is not initialized.

C Because <code>count</code> is not displayed in the template.

D Because <code>afterUpdate</code> changes <code>count</code>, triggering itself repeatedly.

💡 Hint

Think about what triggers Svelte to run afterUpdate again.

Modifying count inside afterUpdate causes a state change.

This triggers another update cycle, which calls afterUpdate again, causing an infinite loop.

🧠 Conceptual

expert

Choosing the correct lifecycle hook for DOM measurement

You want to measure the size of a DOM element after it updates in Svelte. Which lifecycle hook should you use and why?

A <code>beforeUpdate</code>, because it runs before the DOM changes and lets you measure the old size.

B Neither, you should use <code>onMount</code> because it runs once after component loads.

C <code>afterUpdate</code>, because it runs after the DOM updates and lets you measure the new size.

D <code>beforeUpdate</code>, because it runs after the DOM updates and lets you measure the new size.

💡 Hint

Think about when the DOM reflects the latest changes.

afterUpdate runs after the DOM has updated, so you can measure the element's new size accurately.

beforeUpdate runs before the DOM changes, so it measures the old size.

onMount runs only once after initial render, not after updates.

Practice

1. What is the main purpose of the beforeUpdate lifecycle function in Svelte?

easy

A. To run code only once when the component mounts

B. To run code after the component is destroyed

C. To run code just before the DOM updates

D. To run code after the DOM updates

Solution

1. Step 1: Understand lifecycle timing

   The beforeUpdate function runs right before the DOM changes are applied.

2. Step 2: Compare with other lifecycle functions

   afterUpdate runs after DOM updates, and onDestroy runs when the component is removed.

3. Final Answer:

   To run code just before the DOM updates -> Option C

4. Quick Check:

   beforeUpdate = runs before DOM changes [OK]

Hint: beforeUpdate runs before DOM changes, afterUpdate runs after [OK]

Common Mistakes:

• Confusing beforeUpdate with afterUpdate
• Thinking beforeUpdate runs only once
• Mixing lifecycle with component mounting or destruction

2. Which of the following is the correct syntax to import and use beforeUpdate in a Svelte component?

easy

A. import { beforeUpdate } from 'svelte'; beforeUpdate = () => { console.log('Before update'); };

B. import beforeUpdate from 'svelte'; beforeUpdate(() => { console.log('Before update'); });

C. import { beforeUpdate } from 'svelte'; function beforeUpdate() { console.log('Before update'); }

D. import { beforeUpdate } from 'svelte'; beforeUpdate(() => { console.log('Before update'); });

Solution

1. Step 1: Check import syntax

   The correct import uses curly braces: import { beforeUpdate } from 'svelte';

2. Step 2: Check usage syntax

   beforeUpdate is called as a function with a callback: beforeUpdate(() => { ... });

3. Final Answer:

   import { beforeUpdate } from 'svelte'; beforeUpdate(() => { console.log('Before update'); }); -> Option D

4. Quick Check:

   Correct import and callback usage = import { beforeUpdate } from 'svelte'; beforeUpdate(() => { console.log('Before update'); }); [OK]

Hint: Import with braces and call beforeUpdate(callback) [OK]

Common Mistakes:

• Importing without braces
• Assigning beforeUpdate instead of calling it
• Defining a function named beforeUpdate instead of using the imported one

3. Consider this Svelte component code snippet:

import { beforeUpdate, afterUpdate } from 'svelte';

let count = 0;
beforeUpdate(() => {
  console.log('Before:', count);
});
afterUpdate(() => {
  console.log('After:', count);
});

function increment() {
  count += 1;
}

What will be logged to the console after calling increment() once?

medium

A. Before: 0
After: 1

B. Before: 1
After: 1

C. Before: 0
After: 0

D. Before: 1
After: 0

Solution

1. Step 1: Understand when beforeUpdate runs

   The beforeUpdate callback runs before the DOM updates but after the state change. However, the console.log inside beforeUpdate logs the current value of count before the DOM updates, which is the updated value.

2. Step 2: Understand when afterUpdate runs

   The afterUpdate callback runs after the DOM updates, logging the updated value of count.

3. Step 3: Trace the logs

   When increment() is called, count is incremented to 1. Then beforeUpdate runs and logs Before: 0 because the DOM hasn't updated yet, but the variable has changed. Then afterUpdate runs and logs After: 1.

4. Final Answer:

   Before: 0 After: 1 -> Option A

5. Quick Check:

   beforeUpdate logs old DOM state, afterUpdate logs new DOM state [OK]

Hint: beforeUpdate logs old DOM state, afterUpdate logs new DOM state [OK]

Common Mistakes:

• Thinking beforeUpdate logs new value
• Confusing order of logs
• Thinking afterUpdate logs old value

4. This Svelte code tries to log messages before and after updates:

import { beforeUpdate, afterUpdate } from 'svelte';

beforeUpdate = () => console.log('Before update');
afterUpdate(() => console.log('After update'));

What is the problem with this code?

medium

A. afterUpdate is not imported correctly

B. beforeUpdate is overwritten instead of called as a function

C. Missing semicolon after beforeUpdate assignment

D. No problem, code works fine

Solution

1. Step 1: Analyze beforeUpdate usage

   The code assigns a new function to beforeUpdate, overwriting the imported function instead of calling it.

2. Step 2: Check afterUpdate usage

   afterUpdate is correctly called as a function with a callback.

3. Final Answer:

   beforeUpdate is overwritten instead of called as a function -> Option B

4. Quick Check:

   Use beforeUpdate(callback), not assignment [OK]

Hint: Call beforeUpdate(callback), don't assign it [OK]

Common Mistakes:

• Assigning lifecycle functions instead of calling them
• Ignoring import correctness
• Assuming missing semicolon causes error here

5. You want to update a variable status right before the DOM updates and log the new status right after the DOM updates in a Svelte component. Which code snippet correctly achieves this?

hard

A. import { beforeUpdate, afterUpdate } from 'svelte';
beforeUpdate(() => { status = 'updating'; });
afterUpdate(() => { console.log('Status:', status); });

B. import { beforeUpdate, afterUpdate } from 'svelte';
afterUpdate(() => { status = 'updating'; });
beforeUpdate(() => { console.log('Status:', status); });

C. import { beforeUpdate, afterUpdate } from 'svelte';
beforeUpdate(() => { console.log('Status:', status); });
afterUpdate(() => { status = 'updating'; });

D. import { beforeUpdate, afterUpdate } from 'svelte';
beforeUpdate(() => { status = 'updated'; });
afterUpdate(() => { console.log('Status:', 'updating'); });

Solution

1. Step 1: Set variable before DOM updates

   Use beforeUpdate to assign status = 'updating' before the DOM changes.

2. Step 2: Log variable after DOM updates

   Use afterUpdate to log the current status after the DOM updates.

3. Final Answer:

   import { beforeUpdate, afterUpdate } from 'svelte'; beforeUpdate(() => { status = 'updating'; }); afterUpdate(() => { console.log('Status:', status); }); -> Option A

4. Quick Check:

   Update before, log after update [OK]

Hint: Update state in beforeUpdate, log in afterUpdate [OK]

Common Mistakes:

• Swapping beforeUpdate and afterUpdate roles
• Logging before updating the variable
• Using wrong status strings causing confusion