Keyed each blocks in Svelte - Step-by-Step Execution

Concept Flow - Keyed each blocks

Start with array of items

↓

Begin each block with key

↓

For each item in array

↓

Create DOM element linked to key

↓

If array changes

↓

Use keys to match old and new elements

↓

Update, add, or remove elements efficiently

↓

End

This flow shows how Svelte uses keys in each blocks to track items and update the DOM efficiently when the array changes.

Execution Sample

Svelte

<script>
  let fruits = [
    { id: 1, name: 'Apple' },
    { id: 2, name: 'Banana' }
  ];
</script>

{#each fruits as fruit (fruit.id)}
  <p>{fruit.name}</p>
{/each}

This code renders a list of fruits using a keyed each block to track items by their unique id.

Execution Table

Step	Action	Array State	DOM Elements	Notes
1	Initial render	[{id:1,name:'Apple'},{id:2,name:'Banana'}]	<p>Apple</p>, <p>Banana</p>	Create elements for each fruit keyed by id
2	Update array: add {id:3,name:'Cherry'}	[{id:1,name:'Apple'},{id:2,name:'Banana'},{id:3,name:'Cherry'}]	<p>Apple</p>, <p>Banana</p>, <p>Cherry</p>	Add new element for Cherry with key 3
3	Update array: remove {id:1}	[{id:2,name:'Banana'},{id:3,name:'Cherry'}]	<p>Banana</p>, <p>Cherry</p>	Remove element with key 1, keep others
4	Update array: reorder items	[{id:3,name:'Cherry'},{id:2,name:'Banana'}]	<p>Cherry</p>, <p>Banana</p>	Reorder elements using keys to avoid recreating
5	Update array: change name of id 2	[{id:3,name:'Cherry'},{id:2,name:'Blueberry'}]	<p>Cherry</p>, <p>Blueberry</p>	Update text of element with key 2
6	Exit	No further changes	DOM matches array items keyed	All updates done efficiently using keys

💡 No more updates; DOM elements correspond to array items by keys

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	Final
fruits	[{id:1,name:'Apple'},{id:2,name:'Banana'}]	[{id:1,name:'Apple'},{id:2,name:'Banana'},{id:3,name:'Cherry'}]	[{id:2,name:'Banana'},{id:3,name:'Cherry'}]	[{id:3,name:'Cherry'},{id:2,name:'Banana'}]	[{id:3,name:'Cherry'},{id:2,name:'Blueberry'}]	[{id:3,name:'Cherry'},{id:2,name:'Blueberry'}]

Key Moments - 3 Insights

Why do we use a key in the each block?

The key helps Svelte track which DOM elements correspond to which data items, so it can update only what changed instead of rebuilding everything. See execution_table steps 2-5.

What happens if we don't use keys and reorder the array?

Without keys, Svelte may recreate all elements instead of reusing them, causing inefficient updates and losing element state. The keyed approach in step 4 avoids this.

How does Svelte know which element to update when an item changes?

Svelte matches items by their keys and updates only the changed parts, like the name change in step 5 where only the text updates.

Visual Quiz - 3 Questions

Look at the execution_table at step 3. What happens to the DOM elements?

A All elements are recreated

B The element with key 1 is removed

C A new element with key 1 is added

D No changes happen

💡 Hint

Check the 'DOM Elements' and 'Notes' columns at step 3 in execution_table

At which step does the array reorder its items?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Look at the 'Array State' column in execution_table to find when order changes

If we removed the key from the each block, what would likely happen when reordering items?

A Svelte would update only changed items efficiently

B Nothing would change in the DOM

C Svelte would recreate all DOM elements causing inefficiency

D Svelte would throw an error

💡 Hint

Refer to key_moments explanation about the importance of keys for efficient updates

Concept Snapshot

Keyed each blocks in Svelte track list items by a unique key.
Syntax: {#each items as item (key)} ... {/each}
Keys help Svelte update only changed elements.
Without keys, reordering or changes cause full re-renders.
Use keys for efficient, stable DOM updates.

Full Transcript

This lesson shows how Svelte uses keyed each blocks to efficiently update lists. We start with an array of items, each with a unique id used as a key. When rendering, Svelte creates DOM elements linked to these keys. If the array changes by adding, removing, or reordering items, Svelte uses the keys to match old and new elements. This lets it update only what changed, avoiding full re-renders. The execution table traces steps like adding a new fruit, removing one, reordering, and changing a name. The variable tracker shows how the fruits array changes over time. Key moments clarify why keys are important and what happens without them. The quiz tests understanding of these updates and the role of keys. The snapshot summarizes the key points for quick reference.

Practice

1. What is the main purpose of using a keyed each block in Svelte?

easy

A. To prevent the list from rendering

B. To uniquely identify list items for efficient updates

C. To sort the list items automatically

D. To style list items differently

Solution

1. Step 1: Understand what keyed each blocks do

   Keyed each blocks use a unique key to track each item in a list, helping Svelte update only changed items.

2. Step 2: Identify the main purpose

   This unique key helps keep the UI consistent and efficient when the list changes dynamically.

3. Final Answer:

   To uniquely identify list items for efficient updates -> Option B

4. Quick Check:

   Keyed each blocks track items uniquely = D [OK]

Hint: Keys track items uniquely for smooth updates [OK]

Common Mistakes:

• Thinking keys are for styling
• Assuming keys sort items
• Believing keys stop rendering

2. Which of the following is the correct syntax for a keyed each block in Svelte?

easy

A. {#each items as item (item.id)}

B. {#each items as item}

C. {#each items (item.id)}

D. {#each items item.id as item}

Solution

1. Step 1: Recall keyed each block syntax

   The correct syntax uses parentheses after the 'as' clause to specify the key: {#each items as item (item.id)}

2. Step 2: Compare options

   {#each items as item (item.id)} matches the correct syntax exactly, others miss parentheses or order.

3. Final Answer:

   {#each items as item (item.id)} -> Option A

4. Quick Check:

   Key goes in parentheses after 'as' = B [OK]

Hint: Key is inside parentheses after 'as' in each block [OK]

Common Mistakes:

• Omitting parentheses around the key
• Placing key before 'as'
• Using wrong order of parameters

3. Given the code:

{#each users as user (user.id)}
  
{user.name}
{/each}

What happens if the users array changes by adding a new user with a unique id?

medium

A. Only the new user is added to the DOM without re-rendering existing users

B. All users are re-rendered from scratch

C. The list will not update until the page reloads

D. An error occurs because keys must be strings

Solution

1. Step 1: Understand keyed each block behavior on list change

   When a new item with a unique key is added, Svelte updates only that item in the DOM.

2. Step 2: Analyze the effect of adding a new user

   The existing users remain unchanged; only the new user is inserted efficiently.

3. Final Answer:

   Only the new user is added to the DOM without re-rendering existing users -> Option A

4. Quick Check:

   Keyed blocks update only changed items = C [OK]

Hint: New unique keys add items without full re-render [OK]

Common Mistakes:

• Thinking all items re-render on change
• Believing list updates require page reload
• Assuming keys must be strings only

4. Consider this Svelte code snippet:

{#each items as item (item.key)}
  
{item.value}
{/each}

If item.key is not unique for all items, what problem can occur?

medium

A. Svelte will automatically fix duplicate keys

B. The code will throw a syntax error

C. The list will not render at all

D. Svelte may reuse DOM elements incorrectly, causing UI bugs

Solution

1. Step 1: Understand the role of unique keys

   Keys must be unique to correctly track each item; duplicates confuse Svelte's DOM updates.

2. Step 2: Identify the effect of duplicate keys

   With duplicate keys, Svelte may wrongly reuse DOM elements, causing wrong data to show or UI glitches.

3. Final Answer:

   Svelte may reuse DOM elements incorrectly, causing UI bugs -> Option D

4. Quick Check:

   Duplicate keys cause wrong DOM reuse = A [OK]

Hint: Keys must be unique to avoid UI bugs [OK]

Common Mistakes:

• Expecting syntax errors from duplicates
• Thinking list won't render at all
• Assuming Svelte fixes duplicates automatically

5. You have a list of tasks with possible duplicate names but unique IDs. You want to display them with a keyed each block and allow dynamic reordering. Which key should you use and why?

{#each tasks as task (???)}
  
{task.name}
{/each}

hard

A. Use the index like each tasks as task (index) for simplicity

B. Use task.name because names are easier to read

C. Use task.id because IDs are unique and stable keys

D. No key is needed for dynamic lists

Solution

1. Step 1: Identify the best key for dynamic lists

   Keys must be unique and stable to track items correctly during reordering.

2. Step 2: Compare key options

   Task IDs are unique and stable, while names can duplicate and indexes change on reorder.

3. Final Answer:

   Use task.id because IDs are unique and stable keys -> Option C

4. Quick Check:

   Unique stable keys like IDs are best for dynamic lists = A [OK]

Hint: Use unique stable IDs as keys for dynamic lists [OK]

Common Mistakes:

• Using non-unique names as keys
• Using index keys causing wrong updates
• Skipping keys on dynamic lists