Use directive syntax in Svelte - Performance & Optimization

Performance: Use directive syntax

MEDIUM IMPACT

This affects how efficiently Svelte updates the DOM and handles reactive behavior during user interactions.

Binding an input value and reacting to changes

Svelte

<input bind:value={name} />

Svelte's bind directive automatically syncs the input and variable with minimal overhead.

📈 Performance GainReduces event handling code and avoids redundant updates

Binding an input value and reacting to changes

Svelte

<input value={name} on:input={(e) => name = e.target.value} />

Manually handling input events causes extra JavaScript execution and can lead to redundant DOM updates.

📉 Performance CostTriggers multiple event handlers and re-renders on every keystroke

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Manual event handling for input	Multiple event listeners	Multiple reflows per keystroke	High paint cost due to frequent updates	[X] Bad
Svelte bind directive for input	Minimal DOM updates	Single reflow per change	Low paint cost	[OK] Good
CSS visibility toggle for conditional content	DOM nodes remain	Reflows on layout changes	Higher paint cost	[X] Bad
Svelte if directive for conditional content	DOM nodes added/removed	Reflows only when toggled	Lower paint cost	[OK] Good

Rendering Pipeline

Svelte's directive syntax compiles to minimal DOM operations and efficient updates, reducing work in layout and paint stages.

→DOM Updates

→Layout

→Paint

⚠️ BottleneckLayout and Paint caused by unnecessary DOM changes

Core Web Vital Affected

INP

This affects how efficiently Svelte updates the DOM and handles reactive behavior during user interactions.

Optimization Tips

1Use Svelte's bind directive to sync inputs efficiently.

2Use {#if} to conditionally add/remove DOM elements instead of hiding with CSS.

3Avoid manual event handlers when directive syntax can handle updates.

Performance Quiz - 3 Questions

Why is using Svelte's bind directive better than manually handling input events?

A It delays rendering to improve animation smoothness.

B It increases bundle size but improves styling.

C It reduces redundant DOM updates and event handling overhead.

D It disables browser default input behavior.

DevTools: Performance

How to check: Record a performance profile while interacting with inputs or toggling content. Look for layout and paint events.

What to look for: Lower number of layout and paint events indicates better use of directive syntax and fewer DOM updates.

Practice

1. Which Svelte directive is used to conditionally show content based on a boolean value?
{#if}, {#each}, on:, or bind:?

easy

A. bind:

B. {#if}

C. on:

D. {#each}

Solution

1. Step 1: Understand the purpose of {#if}

   The {#if} directive in Svelte shows or hides content based on a condition.

2. Step 2: Compare with other directives

   {#each} loops over lists, on: handles events, and bind: links variables to inputs.

3. Final Answer:

   {#if} -> Option B

4. Quick Check:

   Conditional display = {#if} [OK]

Hint: Use {#if} to show/hide content based on true/false [OK]

Common Mistakes:

• Confusing {#if} with {#each} for loops
• Using on:click for conditional display
• Trying to bind variables for conditionals

2. Which of the following is the correct syntax to listen for a click event on a button in Svelte?

easy

A. <button onClick={handleClick}>Click</button>

B. <button click={handleClick}>Click</button>

C. <button on:click={handleClick}>Click</button>

D. <button bind:click={handleClick}>Click</button>

Solution

1. Step 1: Recall Svelte event directive syntax

   Svelte uses on:eventName={handler} to listen to events like clicks.

2. Step 2: Check each option

   <button on:click={handleClick}>Click</button> uses on:click correctly. Options A, B, and D use incorrect or invalid syntax.

3. Final Answer:

   <button on:click={handleClick}>Click</button> -> Option C

4. Quick Check:

   Event listener syntax = on:event [OK]

Hint: Use on:eventName={handler} to listen for events [OK]

Common Mistakes:

• Using camelCase like onClick instead of on:click
• Trying to bind events with bind:
• Omitting the on: prefix

3. What will be the rendered output of this Svelte code?

<script>
  let items = ['apple', 'banana'];
</script>

<ul>
  {#each items as item}
    <li>{item}</li>
  {/each}
</ul>

medium

A. applebanana

B. items

C. {item}{item}

D. Syntax error

Solution

1. Step 1: Understand the {#each} directive

   The {#each} directive loops over the array items and assigns each element to item.

2. Step 2: Render list items

   For each item, it creates a <li> element with the item text inside.

3. Final Answer:

   <ul><li>apple</li><li>banana</li></ul> -> Option A

4. Quick Check:

   Loop items render as list =
   • apple
   • banana
   [OK]

Hint: Each loops output list items for each array element [OK]

Common Mistakes:

• Expecting the literal string {item} to show
• Confusing the array name with item variable
• Thinking it causes a syntax error

4. Identify the error in this Svelte snippet:

<script>
  let count = 0;
</script>

<button on:click="count++">Increment</button>
<p>Count: {count}</p>

medium

A. Using double quotes around the event handler expression

B. Missing bind: directive on count variable

C. Incorrect variable name count

D. No error, code works fine

Solution

1. Step 1: Check event handler syntax

   Svelte requires event handlers to use curly braces without quotes: on:click={count++}.

2. Step 2: Identify the error

   The code uses quotes around the expression, which causes a syntax error.

3. Final Answer:

   Using double quotes around the event handler expression -> Option A

4. Quick Check:

   Event handler must be unquoted expression [OK]

Hint: Use curly braces, not quotes, for event handlers [OK]

Common Mistakes:

• Putting event handler code inside quotes
• Trying to bind variables unnecessarily
• Assuming variable name is wrong

5. You want to create a Svelte component that shows a list of tasks and lets the user toggle each task's completion status by clicking a checkbox. Which directive syntax combination correctly binds the checkbox state and updates the task's done property?

hard

A. <ul>
{#each tasks as task}
<li>
<input type="checkbox" on:click={task.done = !task.done} /> {task.text}
</li>
{/each}
</ul>

B. <ul>
{#each tasks as task}
<li>
<input type="checkbox" checked={task.done} on:change={() => task.done = !task.done} /> {task.text}
</li>
{/each}
</ul>

C. <ul>
{#each tasks as task}
<li>
<input type="checkbox" bind:value={task.done} /> {task.text}
</li>
{/each}
</ul>

D. <script>
let tasks = [
{ id: 1, text: 'Task 1', done: false },
{ id: 2, text: 'Task 2', done: true }
];
</script>

<ul>
{#each tasks as task}
<li>
<input type="checkbox" bind:checked={task.done} /> {task.text}
</li>
{/each}
</ul>

Solution

1. Step 1: Understand binding checkbox state

   In Svelte, bind:checked links the checkbox's checked state directly to a variable, updating it automatically.

2. Step 2: Analyze each option

   <script>
     let tasks = [
       { id: 1, text: 'Task 1', done: false },
       { id: 2, text: 'Task 2', done: true }
     ];
   </script>
   
   <ul>
     {#each tasks as task}
       <li>
         <input type="checkbox" bind:checked={task.done} /> {task.text}
       </li>
     {/each}
   </ul>

   uses bind:checked={task.done}, which is correct.

   <ul>
     {#each tasks as task}
       <li>
         <input type="checkbox" checked={task.done} on:change={() => task.done = !task.done} /> {task.text}
       </li>
     {/each}
   </ul>

   manually toggles on change but is more complex.

   <ul>
     {#each tasks as task}
       <li>
         <input type="checkbox" bind:value={task.done} /> {task.text}
       </li>
     {/each}
   </ul>

   uses bind:value which is incorrect for checkboxes.

   <ul>
     {#each tasks as task}
       <li>
         <input type="checkbox" on:click={task.done = !task.done} /> {task.text}
       </li>
     {/each}
   </ul>

   uses on:click without binding, which is less reactive.

3. Final Answer:

   bind:checked={task.done} -> Option D

4. Quick Check:

   Checkbox bind:checked updates variable automatically [OK]

Hint: Use bind:checked to sync checkbox with boolean variable [OK]

Common Mistakes:

• Using bind:value instead of bind:checked for checkboxes
• Manually toggling state instead of binding
• Using on:click without reactive binding