Middleware patterns with hooks in Svelte - Performance & Optimization

Performance: Middleware patterns with hooks

MEDIUM IMPACT

This affects the responsiveness and load time by controlling how code runs before and after component rendering.

Running side effects or logic after component mounting

Svelte

import { onMount } from 'svelte';
onMount(async () => {
  await heavyAsyncTask();
});

Using async tasks allows the browser to stay responsive while waiting, improving responsiveness.

📈 Performance Gainnon-blocking main thread, improves INP by reducing main thread blocking

Running side effects or logic after component mounting

Svelte

import { onMount } from 'svelte';
onMount(() => {
  heavySyncTask();
});

Running heavy synchronous tasks inside onMount blocks the main thread, delaying interactivity.

📉 Performance Costblocks main thread for 100+ ms depending on task complexity

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Heavy synchronous tasks in onMount	Minimal	0 but blocks JS thread	High due to blocking	[X] Bad
Async tasks in onMount	Minimal	0	Low	[OK] Good
Multiple separate beforeUpdate hooks updating state	Multiple	2+	High	[X] Bad
Single beforeUpdate hook batching state updates	Multiple	1	Medium	[OK] Good

Rendering Pipeline

Middleware hooks run during component lifecycle stages and can affect style calculation, layout, and paint depending on how they modify state or DOM.

→JavaScript Execution

→Style Calculation

→Layout

→Paint

⚠️ BottleneckJavaScript Execution blocking main thread delays subsequent layout and paint

Core Web Vital Affected

INP

This affects the responsiveness and load time by controlling how code runs before and after component rendering.

Optimization Tips

1Avoid heavy synchronous tasks inside middleware hooks to prevent blocking rendering.

2Batch multiple state updates in a single hook to reduce reflows and repaints.

3Use asynchronous code in hooks to keep the main thread free and improve responsiveness.

Performance Quiz - 3 Questions

What is the main performance risk of running heavy synchronous code inside a Svelte onMount hook?

A It causes excessive network requests

B It increases CSS selector complexity

C It blocks the main thread delaying rendering

D It reduces JavaScript bundle size

DevTools: Performance

How to check: Record a performance profile while loading the component and interacting with it. Look for long tasks blocking the main thread and multiple layout/repaint events.

What to look for: Long blocking JavaScript tasks and multiple layout thrashing events indicate poor middleware hook usage.

Practice

1. Which Svelte hook is best suited to run code right after a component appears on the page?

easy

A. onDestroy

B. onMount

C. afterUpdate

D. beforeUpdate

Solution

1. Step 1: Understand when onMount runs

   onMount runs once right after the component is added to the page.

2. Step 2: Compare with other hooks

   beforeUpdate and afterUpdate run on updates, onDestroy runs when component is removed.

3. Final Answer:

   onMount -> Option B

4. Quick Check:

   Run code after component appears = onMount [OK]

Hint: Use onMount for code after component loads [OK]

Common Mistakes:

• Confusing onMount with beforeUpdate
• Using onDestroy to run code on load
• Thinking afterUpdate runs only once

2. Which is the correct syntax to import and use the onDestroy hook in a Svelte component?

easy

A. import { onDestroy } from 'svelte/hooks'; onDestroy(() => { /* cleanup */ });

B. import onDestroy from 'svelte'; onDestroy(() => { /* cleanup */ });

C. import { onDestroy } from 'svelte'; onDestroy = () => { /* cleanup */ };

D. import { onDestroy } from 'svelte'; onDestroy(() => { /* cleanup */ });

Solution

1. Step 1: Check correct import syntax

   Svelte exports hooks like onDestroy as named exports from 'svelte'.

2. Step 2: Verify usage

   The hook is called as a function with a callback: onDestroy(() => { ... }).

3. Final Answer:

   import { onDestroy } from 'svelte'; onDestroy(() => { /* cleanup */ }); -> Option D

4. Quick Check:

   Named import + callback function = import { onDestroy } from 'svelte'; onDestroy(() => { /* cleanup */ }); [OK]

Hint: Use named import from 'svelte' and call with callback [OK]

Common Mistakes:

• Using default import instead of named import
• Importing from wrong path like 'svelte/hooks'
• Assigning hook to a variable instead of calling it

3. Given this Svelte code snippet, what will be logged to the console when the component updates?

import { beforeUpdate, afterUpdate } from 'svelte';

beforeUpdate(() => console.log('Before update'));
afterUpdate(() => console.log('After update'));

let count = 0;

function increment() {
  count += 1;
}

medium

A. After update only once after first render

B. Only Before update once when component mounts

C. Before update\nAfter update each time increment() is called

D. No logs because hooks are not called

Solution

1. Step 1: Understand when hooks run

   beforeUpdate runs before every DOM update, afterUpdate runs after every DOM update.

2. Step 2: Analyze increment effect

   Calling increment() changes count, triggering component update and both hooks logging messages.

3. Final Answer:

   Before update\nAfter update each time increment() is called -> Option C

4. Quick Check:

   Hooks run on every update = Before update\nAfter update each time increment() is called [OK]

Hint: Hooks run before and after every update triggered by state change [OK]

Common Mistakes:

• Thinking hooks run only once on mount
• Assuming logs happen without calling increment()
• Confusing beforeUpdate and afterUpdate timing

4. What is wrong with this Svelte code using onDestroy?

import { onDestroy } from 'svelte';

onDestroy = () => {
  console.log('Cleanup');
};

medium

A. Assigning a function to onDestroy instead of calling it

B. Missing import statement for onDestroy

C. Using arrow function instead of regular function

D. onDestroy should be used inside onMount

Solution

1. Step 1: Check how onDestroy is used

   The code assigns a function to onDestroy instead of calling it with a callback.

2. Step 2: Correct usage

   onDestroy must be called like onDestroy(() => { ... }) to register cleanup.

3. Final Answer:

   Assigning a function to onDestroy instead of calling it -> Option A

4. Quick Check:

   Use onDestroy(callback), not assignment [OK]

Hint: Call onDestroy with a callback, don't assign it [OK]

Common Mistakes:

• Assigning instead of calling the hook
• Thinking arrow functions are disallowed
• Believing onDestroy must be inside onMount

5. You want to log a message every time a Svelte component updates but only after the DOM has changed. Which hook should you use and why? Also, how would you ensure cleanup if needed?

hard

A. Use afterUpdate to log after DOM changes; use onDestroy for cleanup

B. Use beforeUpdate to log after DOM changes; no cleanup needed

C. Use onMount to log after DOM changes; cleanup inside afterUpdate

D. Use onDestroy to log after DOM changes; cleanup inside beforeUpdate

Solution

1. Step 1: Identify hook for after DOM update

   afterUpdate runs after the DOM updates, perfect for logging post-change.

2. Step 2: Determine cleanup hook

   onDestroy runs when component is removed, ideal for cleanup tasks.

3. Final Answer:

   Use afterUpdate to log after DOM changes; use onDestroy for cleanup -> Option A

4. Quick Check:

   Log after DOM update = afterUpdate; cleanup = onDestroy [OK]

Hint: Log in afterUpdate; cleanup in onDestroy [OK]

Common Mistakes:

• Using beforeUpdate to log after DOM changes
• Trying to cleanup inside afterUpdate
• Confusing onMount with update hooks