Immutable patterns for updates in Svelte - Step-by-Step Execution

Concept Flow - Immutable patterns for updates

Start with original data

↓

Create a copy of data

↓

Modify the copy

↓

Assign the copy back to state

↓

UI updates with new state

↓

End

This flow shows how to update data immutably by copying, changing the copy, then updating state to trigger UI refresh.

Execution Sample

Svelte

let items = [1, 2, 3];

function addItem(newItem) {
  items = [...items, newItem];
}

This code adds a new item to the list immutably by creating a new array copy with the new item.

Execution Table

Step	Action	items Before	Operation	items After	UI Update
1	Initial state	[1, 2, 3]	None	[1, 2, 3]	UI shows 1, 2, 3
2	Call addItem(4)	[1, 2, 3]	Create new array [...items, 4]	[1, 2, 3, 4]	UI updates to show 1, 2, 3, 4
3	Call addItem(5)	[1, 2, 3, 4]	Create new array [...items, 5]	[1, 2, 3, 4, 5]	UI updates to show 1, 2, 3, 4, 5
4	No further calls	[1, 2, 3, 4, 5]	No operation	[1, 2, 3, 4, 5]	UI remains unchanged

💡 No more updates; state remains stable and UI reflects latest state.

Variable Tracker

Variable	Start	After addItem(4)	After addItem(5)	Final
items	[1, 2, 3]	[1, 2, 3, 4]	[1, 2, 3, 4, 5]	[1, 2, 3, 4, 5]

Key Moments - 2 Insights

Why do we create a new array instead of modifying the original 'items' array?

Because Svelte detects changes by comparing references. Changing the original array in place won't trigger UI updates, but assigning a new array does, as shown in steps 2 and 3 of the execution_table.

What happens if we push to the original array instead of creating a new one?

The UI will not update because the reference to 'items' stays the same. Svelte won't detect the change, unlike when we assign a new array as in the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table at step 2. What is the value of 'items' after addItem(4)?

A [4]

B [1, 2, 3, 4]

C [1, 2, 3]

D [1, 2, 3, 5]

💡 Hint

Check the 'items After' column in step 2 of the execution_table.

At which step does the UI first update to include the number 5?

A Step 3

B Step 2

C Step 4

D Never

💡 Hint

Look at the 'UI Update' column in the execution_table for when 5 appears.

If we changed the code to use items.push(newItem) instead of creating a new array, what would happen?

A UI updates correctly every time

B UI updates only on first change

C UI does not update because reference is unchanged

D Code throws an error

💡 Hint

Refer to the key_moments section explaining why immutable updates trigger UI refresh.

Concept Snapshot

Immutable updates in Svelte:
- Always create a new copy of data (e.g., [...items])
- Modify the copy, then assign it back
- This triggers Svelte to update the UI
- Avoid mutating original data directly
- Helps keep UI in sync with state changes

Full Transcript

This lesson shows how to update data immutably in Svelte. Instead of changing the original array, we create a new copy with the changes and assign it back. This lets Svelte detect the change and update the UI. The example adds items to a list by making a new array each time. The execution table traces each step: starting with the original list, adding items immutably, and the UI updating accordingly. Key points include why direct mutation does not update the UI and how immutable patterns solve this. The quiz tests understanding of state changes and UI updates based on the execution trace.

Practice

1. In Svelte, why do we prefer immutable updates when changing state like arrays or objects?

easy

A. Because Svelte does not support mutable updates at all.

B. Because mutable updates are faster and recommended for performance.

C. Because immutable updates prevent any changes to the data forever.

D. Because creating new arrays or objects helps Svelte detect changes and update the UI.

Solution

1. Step 1: Understand Svelte's reactivity system

   Svelte tracks changes by comparing references of variables. If the reference changes, it knows to update the UI.

2. Step 2: Why immutable updates help

   Creating new arrays or objects changes the reference, so Svelte detects the change and updates the screen correctly.

3. Final Answer:

   Because creating new arrays or objects helps Svelte detect changes and update the UI. -> Option D

4. Quick Check:

   Immutable updates = UI updates detected [OK]

Hint: Immutable means new object/array to trigger UI update [OK]

Common Mistakes:

• Thinking mutable updates automatically update UI
• Believing Svelte forbids mutable updates
• Confusing immutability with data never changing

2. Which of the following is the correct way to immutably update an array in Svelte by adding a new item 4 to numbers?

easy

A. numbers.push(4);

B. numbers = [...numbers, 4];

C. numbers[3] = 4;

D. numbers.concat(4);

Solution

1. Step 1: Check each option for immutability

   numbers.push(4); uses push which mutates the original array. numbers[3] = 4; directly assigns an index, mutating the array. numbers.concat(4); calls concat but does not assign the result back, so no update happens.

2. Step 2: Identify the correct immutable update

   numbers = [...numbers, 4]; uses the spread operator to create a new array with the old items plus 4, then assigns it back to numbers, which is the correct immutable pattern.

3. Final Answer:

   numbers = [...numbers, 4]; -> Option B

4. Quick Check:

   Spread operator creates new array [OK]

Hint: Use spread operator and assign new array for immutable update [OK]

Common Mistakes:

• Using push which mutates original array
• Not assigning result of concat back
• Directly modifying array indexes

3. Given this Svelte code:

let todos = [
  { id: 1, text: 'Buy milk', done: false },
  { id: 2, text: 'Walk dog', done: false }
];

// Update to mark todo with id 2 as done
todos = todos.map(todo => todo.id === 2 ? { ...todo, done: true } : todo);

What will be the value of todos after this update?

medium

A. [{ id: 1, text: 'Buy milk', done: false }, { id: 2, text: 'Walk dog', done: true }]

B. [{ id: 1, text: 'Buy milk', done: true }, { id: 2, text: 'Walk dog', done: false }]

C. [{ id: 1, text: 'Buy milk', done: false }, { id: 2, text: 'Walk dog', done: false }]

D. [{ id: 1, text: 'Buy milk', done: true }, { id: 2, text: 'Walk dog', done: true }]

Solution

1. Step 1: Understand the map update logic

   The map goes through each todo. If the todo's id is 2, it creates a new object with done set to true. Otherwise, it returns the original todo unchanged.

2. Step 2: Apply the update to each todo

   Todo with id 1 remains unchanged with done: false. Todo with id 2 is updated to done: true.

3. Final Answer:

   [{ id: 1, text: 'Buy milk', done: false }, { id: 2, text: 'Walk dog', done: true }] -> Option A

4. Quick Check:

   Only todo with id 2 is marked done [OK]

Hint: map + spread updates only matching item immutably [OK]

Common Mistakes:

• Updating wrong todo item
• Mutating original todo instead of creating new
• Not returning updated todo in map

4. What is wrong with this Svelte code that tries to immutably update an object state?

let user = { name: 'Alice', age: 25 };

// Update age
user.age = 26;
user = user;

medium

A. Svelte requires a special function to update objects immutably.

B. Assigning user = user creates a new object reference, so update works fine.

C. Directly modifying user.age mutates the original object, so Svelte may not detect the change.

D. The code correctly uses immutable update patterns.

Solution

1. Step 1: Identify mutation in the code

   The line user.age = 26 directly changes the existing object, which is a mutation.

2. Step 2: Understand Svelte's change detection

   Assigning user = user does not change the reference, so Svelte does not detect any change and will not update the UI.

3. Final Answer:

   Directly modifying user.age mutates the original object, so Svelte may not detect the change. -> Option C

4. Quick Check:

   Mutating object without new reference breaks reactivity [OK]

Hint: Always create new object to update state immutably [OK]

Common Mistakes:

• Mutating object properties directly
• Assigning same object reference back
• Expecting UI to update without new object

5. You have a nested state object in Svelte:

let profile = {
  name: 'Bob',
  address: { city: 'NY', zip: '10001' }
};

// You want to update zip to '10002' immutably. Which is correct?

hard

A. profile = { ...profile, address: { ...profile.address, zip: '10002' } };

B. profile.address.zip = '10002'; profile = profile;

C. profile = { ...profile, zip: '10002' };

D. profile.address = { zip: '10002' }; profile = profile;

Solution

1. Step 1: Understand nested immutable update

   To update a nested property immutably, create new copies of each level: first the nested object, then the outer object.

2. Step 2: Analyze each option

   profile.address.zip = '10002'; profile = profile; mutates nested property directly, no new reference. profile = { ...profile, zip: '10002' }; updates zip at top level, ignoring nesting. profile.address = { zip: '10002' }; profile = profile; replaces address with incomplete object, losing city. profile = { ...profile, address: { ...profile.address, zip: '10002' } }; correctly creates new address object with updated zip, then new profile object.

3. Final Answer:

   profile = { ...profile, address: { ...profile.address, zip: '10002' } }; -> Option A

4. Quick Check:

   Nested spread creates new objects immutably [OK]

Hint: Spread nested objects to update deeply immutably [OK]

Common Mistakes:

• Mutating nested properties directly
• Not copying nested objects fully
• Losing other nested properties by overwriting