Named actions in Svelte - Performance & Optimization

Performance: Named actions

MEDIUM IMPACT

Named actions affect how efficiently DOM elements are enhanced with behavior, impacting interaction responsiveness and layout stability.

Attaching reusable behavior to DOM elements in Svelte

Svelte

function focus(node, params) {
  if (params?.shouldFocus) {
    node.focus();
  }
  return {
    update(params) {
      if (params?.shouldFocus) {
        node.focus();
      }
    }
  };
}

// Usage in component
<input use:focus={{ shouldFocus: true }} />

Focus is only applied when needed, reducing unnecessary DOM operations and layout recalculations.

📈 Performance GainSingle reflow on initial focus, no repeated layout thrashing on updates.

Attaching reusable behavior to DOM elements in Svelte

Svelte

function focus(node) {
  node.focus();
  return {
    update() {
      node.focus();
    }
  };
}

// Usage in component (with frequently changing param)
<input use:focus={counter} />
<!-- counter changes frequently, triggering update every time -->

This action forces focus on every action update (when params change), causing repeated layout recalculations and potential input focus flicker.

📉 Performance CostTriggers multiple reflows on each update, increasing INP and causing input lag.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Unconditional focus on update	Multiple focus calls	Multiple reflows per update	High paint cost due to layout shifts	[X] Bad
Conditional focus only when needed	Single focus call	Single reflow on initial focus	Low paint cost, stable layout	[OK] Good

Rendering Pipeline

Named actions run during the update phase of Svelte components, modifying DOM nodes. If they cause style or layout changes, they trigger reflows and repaints.

→Update

→Layout

→Paint

⚠️ BottleneckLayout (reflow) caused by DOM changes in action update calls

Core Web Vital Affected

INP

Named actions affect how efficiently DOM elements are enhanced with behavior, impacting interaction responsiveness and layout stability.

Optimization Tips

1Avoid unconditional DOM updates inside named actions.

2Use parameters to control when actions update the DOM.

3Monitor reflows caused by actions using browser DevTools.

Performance Quiz - 3 Questions

What is the main performance risk when a named action's update function unconditionally updates the DOM every time its parameters change?

A It delays the initial page load (LCP).

B It causes repeated layout recalculations (reflows), slowing interaction responsiveness.

C It increases the JavaScript bundle size significantly.

D It causes cumulative layout shifts (CLS).

DevTools: Performance

How to check: Record a performance profile while interacting with the component using named actions. Look for layout thrashing or repeated style recalculations.

What to look for: Check for multiple Layout events and long tasks caused by action updates triggering reflows.

Practice

1. What is the main purpose of named actions in Svelte?

easy

A. To style elements with CSS

B. To define new components

C. To add reusable behavior to HTML elements

D. To manage application state

Solution

1. Step 1: Understand what named actions do

   Named actions in Svelte are used to add behavior to HTML elements that can be reused across components.

2. Step 2: Compare with other options

   Defining components, styling, and state management are handled differently in Svelte, not by named actions.

3. Final Answer:

   To add reusable behavior to HTML elements -> Option C

4. Quick Check:

   Named actions = reusable element behavior [OK]

Hint: Named actions add behavior to elements, not styles or state [OK]

Common Mistakes:

• Confusing actions with components
• Thinking actions handle styling
• Assuming actions manage state

2. Which of the following is the correct syntax to define a named action in Svelte?

easy

A. function myAction(node) { /* code */ }

B. const myAction = () => { /* code */ }

C. let myAction = node => { /* code */ }

D. action myAction(node) { /* code */ }

Solution

1. Step 1: Recall named action syntax

   Named actions are functions that receive the element node as the first argument, typically declared as function myAction(node) {}.

2. Step 2: Check other options

   Arrow functions can work but must return an object for cleanup; action myAction(node) { /* code */ } uses invalid syntax.

3. Final Answer:

   function myAction(node) { /* code */ } -> Option A

4. Quick Check:

   Named action = function with node parameter [OK]

Hint: Named actions are functions with node parameter, not keywords [OK]

Common Mistakes:

• Using invalid 'action' keyword
• Defining without node parameter
• Using arrow function without return object

3. Given this named action and usage:

function highlight(node) {
  node.style.backgroundColor = 'yellow';
  return {
    destroy() {
      node.style.backgroundColor = '';
    }
  };
}

<div use:highlight>Hello</div>

What happens when the component is removed from the page?

medium

A. The background color resets to default

B. The element is removed from the DOM immediately

C. An error occurs because destroy is missing

D. The background color stays yellow

Solution

1. Step 1: Understand the action's destroy method

   The destroy method resets the background color to empty string when the element is removed.

2. Step 2: Effect on component removal

   When the component unmounts, destroy runs, so the background color resets to default.

3. Final Answer:

   The background color resets to default -> Option A

4. Quick Check:

   destroy resets styles on removal [OK]

Hint: Destroy cleans up styles when element is removed [OK]

Common Mistakes:

• Assuming styles persist after removal
• Thinking destroy is optional
• Confusing destroy with element removal

4. What is wrong with this named action code?

function focus(node) {
  node.focus();
  return {
    destroy() {
      node.blur();
    }
  }
}

<input use:focus>

medium

A. Calling node.blur() in destroy may cause errors if node is removed

B. The action should not call node.focus() immediately

C. The action does not return an object

D. The action must be async to work properly

Solution

1. Step 1: Analyze the focus call timing

   Calling node.focus() immediately may not work reliably because the element might not be fully rendered, visible, or ready (e.g., during CSS transitions or animations).

2. Step 2: Best practice for focus actions

   In Svelte, it's often necessary to delay the focus call using tick(), requestAnimationFrame, or setTimeout(..., 0) to ensure DOM readiness.

3. Final Answer:

   The action should not call node.focus() immediately -> Option B

4. Quick Check:

   Delay focus with tick() or RAF [OK]

Hint: Delay node.focus() with tick() for reliability [OK]

Common Mistakes:

• Calling focus immediately without delay
• Ignoring DOM/transition timing issues
• Assuming focus always succeeds synchronously

5. You want to create a named action that changes an element's text color based on a parameter and updates it when the parameter changes. Which approach is correct?

hard

A. Use a reactive statement inside the action function to watch parameters

B. Set the color once in the action and ignore parameter changes

C. Recreate the action every time parameters change instead of updating

D. Return an update function from the action that sets the color when parameters change

Solution

1. Step 1: Understand parameter updates in named actions

   Named actions can return an update function to handle parameter changes dynamically.

2. Step 2: Evaluate options for handling parameter changes

   Setting color once ignores updates; reactive statements inside action function don't track parameters; recreating action is inefficient.

3. Final Answer:

   Return an update function from the action that sets the color when parameters change -> Option D

4. Quick Check:

   Use update() to handle parameter changes [OK]

Hint: Use update() function to react to parameter changes [OK]

Common Mistakes:

• Ignoring parameter updates
• Misusing reactive statements inside actions
• Recreating actions unnecessarily