Derived values with $: in Svelte - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the $: syntax do in Svelte?

It creates a reactive statement that automatically re-runs whenever the variables it depends on change.

beginner

How do you declare a derived value that updates when its dependencies change in Svelte?

Use the $: label followed by an assignment or expression that depends on reactive variables.

beginner

Given <code>let count = 1;</code> and <code>$: double = count * 2;</code>, what happens when <code>count</code> changes?

The variable double automatically updates to twice the new count value.

intermediate

Can you use $: to run code that does not assign a value but reacts to changes?

Yes, you can write reactive statements without assignments to run code whenever dependencies change, like logging or calling functions.

intermediate

Why is using $: for derived values better than manually updating variables in Svelte?

Because it keeps your code simple and automatic, avoiding bugs from forgetting to update values and improving readability.

What triggers a reactive statement with $: to re-run in Svelte?

A When any variable it depends on changes

B Only when the component mounts

C When the user clicks a button

D When the page reloads

Reactive statements re-run automatically whenever any of their dependent variables change.

Which of these is a correct way to declare a derived value in Svelte?

A $: total = price * quantity;

B let $total = price + quantity;

C const $: sum = price + quantity;

D function $: sum() { return price + quantity; }

The $: label is used before an assignment to create a reactive derived value.

Can you have multiple reactive statements with $: in one Svelte component?

A Only if they are inside functions.

B No, only one $: statement is allowed.

C Yes, you can have many reactive statements.

D Only if they use different variable names.

Svelte allows multiple reactive statements to handle different derived values or side effects.

What happens if a reactive statement does not assign a value but calls a function?

A The function never runs.

B The function runs whenever dependencies change.

C The function runs only once.

D It causes an error.

Reactive statements can run code like functions whenever their dependencies update.

Why should you prefer $: reactive statements over manual updates?

A They only work with numbers.

B They run slower but are easier to write.

C They require more code but are clearer.

D They automatically keep values in sync and reduce bugs.

Reactive statements automatically update derived values, making code simpler and less error-prone.

Explain how the $: syntax helps manage derived values in Svelte.

Think about how changes in one variable affect others without manual code.

Describe a scenario where you would use a reactive statement without assigning a value.

Consider when you want to run code on changes but don't need a new variable.

Practice

1. What does the $: label do in Svelte?

easy

A. It defines a function that runs only once when the component loads.

B. It declares a variable that cannot be changed.

C. It imports external libraries into the component.

D. It creates a reactive statement that updates automatically when dependencies change.

Solution

1. Step 1: Understand the role of $: in Svelte

   The $: label marks a reactive statement that runs whenever its dependencies change.

2. Step 2: Compare with other options

   Options B, C, and D describe unrelated features: constants, imports, and lifecycle functions, not reactive statements.

3. Final Answer:

   It creates a reactive statement that updates automatically when dependencies change. -> Option D

4. Quick Check:

   Reactive statements = It creates a reactive statement that updates automatically when dependencies change. [OK]

Hint: Remember: $: means auto-update when data changes [OK]

Common Mistakes:

• Thinking $: declares constants
• Confusing $: with imports or functions
• Believing it runs only once

2. Which of the following is the correct syntax to create a reactive derived value double from count in Svelte?

easy

A. let $double = count * 2;

B. $: double = count * 2;

C. const double = $: count * 2;

D. double = $count * 2;

Solution

1. Step 1: Identify correct reactive syntax

   In Svelte, reactive statements start with $: followed by an assignment. So $: double = count * 2; is correct.

2. Step 2: Check other options for syntax errors

   let $double = count * 2; wrongly uses let $double, which is invalid. const double = $: count * 2; misplaces $:. double = $count * 2; uses $count which is incorrect syntax.

3. Final Answer:

   $: double = count * 2; -> Option B

4. Quick Check:

   Reactive assignment = $: double = count * 2; [OK]

Hint: Reactive statements start with $: followed by assignment [OK]

Common Mistakes:

• Using $ inside variable names
• Placing $: after the variable
• Confusing reactive syntax with normal variable declarations

3. Given the code:

let count = 3;
$: double = count * 2;
count = 5;

What is the value of double after count changes?

medium

A. 10

B. 3

C. 6

D. Undefined

Solution

1. Step 1: Understand reactive update

   Initially, count is 3, so double is 6. When count changes to 5, the reactive statement recalculates double as 5 * 2 = 10.

2. Step 2: Confirm final value of double

   After the update, double is 10, reflecting the latest count.

3. Final Answer:

   10 -> Option A

4. Quick Check:

   double = count * 2 = 10 [OK]

Hint: Reactive values update immediately when dependencies change [OK]

Common Mistakes:

• Assuming double stays at initial value
• Thinking reactive statements run only once
• Confusing variable assignment timing

4. Identify the error in this Svelte code snippet:

let a = 2;
$: b = a + 3
$: c = b * 2;

medium

A. Missing semicolon after b = a + 3 causes syntax error.

B. Reactive statements cannot depend on other reactive variables.

C. No error; code works correctly.

D. Variables a, b, and c must be declared with const.

Solution

1. Step 1: Check syntax and reactive dependencies

   In Svelte, semicolons are optional. Reactive statements can depend on other reactive variables like b.

2. Step 2: Verify variable declarations

   Variables can be declared with let and updated reactively. No need for const here.

3. Final Answer:

   No error; code works correctly. -> Option C

4. Quick Check:

   Reactive chaining allowed = No error; code works correctly. [OK]

Hint: Svelte allows reactive statements to depend on other reactive values [OK]

Common Mistakes:

• Expecting mandatory semicolons
• Believing reactive variables can't chain
• Forcing const declarations unnecessarily

5. You want to create a reactive derived value status that shows "High" if score is above 80, "Medium" if between 50 and 80, and "Low" otherwise. Which Svelte code correctly implements this?

hard

A. $: status = score > 80 ? 'High' : score >= 50 ? 'Medium' : 'Low';

B. if (score > 80) { status = 'High'; } else if (score >= 50) { status = 'Medium'; } else { status = 'Low'; }

C. let status = $: score > 80 ? 'High' : score >= 50 ? 'Medium' : 'Low';

D. $: status = (score > 80 && 'High') || (score > 80 && 'Medium') || 'Low';

Solution

1. Step 1: Check reactive statement syntax

   $: status = score > 80 ? 'High' : score >= 50 ? 'Medium' : 'Low'; uses a single reactive assignment with nested ternary operators, which is valid and concise.

2. Step 2: Evaluate other options

   let status = $: score > 80 ? 'High' : score >= 50 ? 'Medium' : 'Low'; incorrectly combines let and $:. if (score > 80) { status = 'High'; } else if (score >= 50) { status = 'Medium'; } else { status = 'Low'; } uses an if-else block but lacks $: label for reactivity. $: status = (score > 80 && 'High') || (score > 80 && 'Medium') || 'Low'; uses logical operators with duplicate conditions that never produce 'Medium'.

3. Final Answer:

   $: status = score > 80 ? 'High' : score >= 50 ? 'Medium' : 'Low'; -> Option A

4. Quick Check:

   Correct reactive ternary = $: status = score > 80 ? 'High' : score >= 50 ? 'Medium' : 'Low'; [OK]

Hint: Use nested ternary inside $: for concise reactive logic [OK]

Common Mistakes:

• Omitting $: for reactive statements
• Mixing let with $: incorrectly
• Using if-else without reactive label