Auto-subscription with $ prefix in Svelte - Performance & Optimization

Performance: Auto-subscription with $ prefix

MEDIUM IMPACT

This affects how reactive updates trigger DOM changes and browser rendering performance.

Reactively updating UI when a store value changes

Svelte

import { writable } from 'svelte/store';
const count = writable(0);

// In component template or script
// Use $count directly to auto-subscribe and update UI reactively

<p>{$count}</p>

Auto-subscription with $ prefix lets Svelte track dependencies and update UI efficiently without manual subscription code.

📈 Performance GainSingle reactivity update per change; avoids redundant reflows and memory leaks

Reactively updating UI when a store value changes

Svelte

import { writable } from 'svelte/store';
const count = writable(0);

let currentCount;
const unsubscribe = count.subscribe(value => {
  currentCount = value;
  // manually update UI or trigger re-render
});

// Use currentCount in template

// Remember to unsubscribe when no longer needed
// unsubscribe();

Manually subscribing requires extra code and can cause unnecessary re-renders or memory leaks if unsubscribed incorrectly.

📉 Performance CostTriggers multiple reflows if subscription updates cause repeated DOM writes; manual subscription overhead

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Manual subscription with subscribe()	Multiple DOM writes if not batched	Multiple reflows per update	Higher paint cost due to repeated updates	[X] Bad
Auto-subscription with $ prefix	Single DOM write per reactive change	Single reflow per update	Lower paint cost due to efficient batching	[OK] Good

Rendering Pipeline

When a store value changes, the $ prefix auto-subscription triggers Svelte's reactive system to schedule updates. This updates the virtual DOM and then the real DOM efficiently.

→Dependency Tracking

→Update Scheduling

→DOM Update

→Paint

⚠️ BottleneckDOM Update stage if many reactive updates happen simultaneously

Core Web Vital Affected

INP

This affects how reactive updates trigger DOM changes and browser rendering performance.

Optimization Tips

1Use $ prefix to auto-subscribe to stores for efficient reactive updates.

2Avoid manual subscriptions unless necessary to prevent memory leaks.

3Batch updates to minimize layout thrashing and reflows.

Performance Quiz - 3 Questions

What is the main performance benefit of using the $ prefix for store values in Svelte?

A It prevents any DOM updates from happening.

B It delays updates to reduce CPU usage.

C It automatically subscribes and updates UI efficiently without manual code.

D It bundles store code separately to reduce file size.

DevTools: Performance

How to check: Record a performance profile while interacting with the component. Look for the number of style recalculations and layout events triggered by store updates.

What to look for: Fewer layout recalculations and shorter scripting times indicate efficient reactive updates with $ prefix.

Practice

1. What does the $ prefix do when used with a Svelte store inside a component?

easy

A. It automatically subscribes to the store and updates the value reactively.

B. It creates a new store with the same value.

C. It unsubscribes from the store to stop updates.

D. It converts the store value to a string.

Solution

1. Step 1: Understand the role of the $ prefix

   The $ prefix in Svelte is used to auto-subscribe to a store and unwrap its current value.

2. Step 2: Recognize reactive updates

   Using $store makes the component update automatically when the store value changes, without manual subscription.

3. Final Answer:

   It automatically subscribes to the store and updates the value reactively. -> Option A

4. Quick Check:

   Auto-subscription = It automatically subscribes to the store and updates the value reactively. [OK]

Hint: Remember: $ means auto-subscribe and unwrap store value [OK]

Common Mistakes:

• Thinking $ creates a new store
• Believing $ unsubscribes from the store
• Assuming $ converts value to string

2. Which of the following is the correct syntax to use the $ prefix with a Svelte store named count inside a component?

easy

A. let value = count.$;

B. let value = count$;

C. let value = $count;

D. let value = $count();

Solution

1. Step 1: Identify correct $ prefix usage

   The $ prefix is placed directly before the store variable name to unwrap its value, like $count.

2. Step 2: Check syntax correctness

   let value = $count; uses let value = $count; which is valid syntax to get the current store value reactively.

3. Final Answer:

   let value = $count; -> Option C

4. Quick Check:

   Correct $ prefix syntax = let value = $count; [OK]

Hint: Place $ directly before store name, no parentheses [OK]

Common Mistakes:

• Putting $ after the store name
• Using $ as a method call
• Adding dot before $

3. Given the following Svelte code snippet, what will be displayed when the button is clicked twice?

  
   count.update(n => n + 1)}>Increment
  
Count: {$count}

medium

A. Count: undefined

B. Count: 1

C. Count: 0

D. Count: 2

Solution

1. Step 1: Understand the initial state and update

   The store count starts at 0. Each button click increases it by 1 using count.update(n => n + 1).

2. Step 2: Calculate value after two clicks

   After two clicks, the value increments twice: 0 + 1 + 1 = 2. The {$count} auto-subscribes and shows the current value.

3. Final Answer:

   Count: 2 -> Option D

4. Quick Check:

   2 increments = Count: 2 [OK]

Hint: Each click adds 1; $count shows current value [OK]

Common Mistakes:

• Forgetting the store updates on click
• Thinking $count is static
• Assuming initial value stays

4. What is the error in the following Svelte code using the $ prefix?

  
  
Hello, {currentName}!
   name.set('Bob')}>Change Name

medium

A. The store name cannot be updated with set.

B. The variable currentName should use $name to auto-subscribe.

C. The on:click event is missing parentheses.

D. The import statement is incorrect.

Solution

1. Step 1: Identify how to access store value reactively

   The variable currentName is assigned the store itself, not its value. To get the current value reactively, it should be let currentName = $name;.

2. Step 2: Understand the effect on UI

   Without $, currentName is the store object, so the UI shows it incorrectly and does not update on changes.

3. Final Answer:

   The variable currentName should use $name to auto-subscribe. -> Option B

4. Quick Check:

   Use $ to unwrap store value = The variable currentName should use $name to auto-subscribe. [OK]

Hint: Use $ prefix to unwrap store value for reactive variables [OK]

Common Mistakes:

• Assigning store object instead of its value
• Forgetting $ prefix for reactive updates
• Misunderstanding store.set usage

5. You have two writable stores in Svelte: countA and countB. You want to display their sum reactively in a component. Which is the correct way to do this using the $ prefix?

  
  
  
Sum: ???

hard

A. <p>Sum: {$countA + $countB}</p>

B. <p>Sum: {countA + countB}</p>

C. <p>Sum: {$countA + countB}</p>

D. <p>Sum: {countA.get() + countB.get()}</p>

Solution

1. Step 1: Understand how to unwrap multiple stores

   Using $countA and $countB unwraps their current values reactively.

2. Step 2: Combine unwrapped values in expression

   Adding $countA + $countB inside curly braces calculates the sum reactively and updates UI on changes.

3. Final Answer:

   <p>Sum: {$countA + $countB}</p> -> Option A

4. Quick Check:

   Use $ on both stores to sum reactively = <p>Sum: {$countA + $countB}</p> [OK]

Hint: Use $ on each store to unwrap before adding [OK]

Common Mistakes:

• Adding store objects instead of values
• Mixing $ prefix on only one store
• Using .get() which is not a Svelte store method