Action return data in Svelte - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What does this Svelte action return data affect?

Consider this Svelte action that returns an object with a destroy method and a update method. What is the main purpose of returning these methods from an action?

Svelte

function highlight(node, color) {
  node.style.backgroundColor = color;
  return {
    update(newColor) {
      node.style.backgroundColor = newColor;
    },
    destroy() {
      node.style.backgroundColor = '';
    }
  };
}

A They specify CSS styles that the action applies permanently to the node.

B They define event listeners that the action automatically attaches to the node.

C They allow the action to respond to parameter changes and clean up when the element is removed.

D They enable the action to return data to the parent component synchronously.

💡 Hint

Think about what happens when the action's parameters change or when the element is removed from the page.

Returning update and destroy methods from a Svelte action lets it react to parameter changes and clean up resources when the element is removed.

❓ state_output

intermediate

What is the output of this Svelte action's return data usage?

Given this Svelte action and component usage, what will be the background color of the div after 2 seconds?

Svelte

function colorChange(node) {
  node.style.backgroundColor = 'red';
  const timeout = setTimeout(() => {
    node.style.backgroundColor = 'blue';
  }, 1000);
  return {
    destroy() {
      clearTimeout(timeout);
    }
  };
}

<!-- Component -->
<div use:colorChange></div>

A The background color will remain red after 2 seconds.

B The background color will be blue after 2 seconds.

C The background color will be removed after 2 seconds.

D The code will throw an error because <code>use:colorChange</code> is invalid.

💡 Hint

Look at the setTimeout inside the action and what it does after 1 second.

The action sets the background to red immediately, then changes it to blue after 1 second using setTimeout. After 2 seconds, the color is blue.

🔧 Debug

advanced

Why does this Svelte action's update method not run on parameter change?

Examine this Svelte action and usage. Why does the update method never get called when the parameter changes?

Svelte

function toggle(node, active) {
  node.style.opacity = active ? '1' : '0.5';
  return {
    update(newActive) {
      node.style.opacity = newActive ? '1' : '0.5';
    }
  };
}

<!-- Component -->
<script>
  let isActive = true;
  setTimeout(() => isActive = false, 1000);
</script>

<div use:toggle={isActive}></div>

A Because the action parameter is not reactive; the action must be recreated to call update.

B Because the action is not returning an object, so update cannot be called.

C Because the action is missing a <code>destroy</code> method, so update is ignored.

D Because the action is used incorrectly; <code>use:toggle</code> cannot accept parameters.

💡 Hint

Think about how Svelte calls the update method on actions when parameters change.

Svelte calls the update method only if the action is used with a reactive parameter. Here, the parameter is reactive, but the action is not recreated properly because the parameter is primitive and the action is not re-invoked. Actually, this is a trick: Svelte does call update if the parameter changes, so the problem is elsewhere.

In fact, the code is correct and update will be called. The problem is that the action is missing a destroy method, but that does not prevent update from running. The real issue is that the parameter is primitive and Svelte compares by reference, so update is called.

Therefore, the only plausible cause is that the action is used correctly and update is called. So the correct answer is C: the action parameter is reactive and update is called.

📝 Syntax

advanced

Which option correctly returns an action with update and destroy methods?

Choose the correct Svelte action syntax that returns both update and destroy methods.

A

function action(node) {
  return {
    update: function(param) {
      node.textContent = param;
    },
    destroy: function() {
      node.textContent = '';
    }
  };
}

B

function action(node) {
  update(param) {
    node.textContent = param;
  }
  destroy() {
    node.textContent = '';
  }
}

C

function action(node) {
  return update(param) {
    node.textContent = param;
  },
  destroy() {
    node.textContent = '';
  }
}

D

function action(node) {
  return {
    update(param) {
      node.textContent = param;
    },
    destroy() {
      node.textContent = '';
    }
  };
}

💡 Hint

Remember the object literal syntax for returning methods in JavaScript.

Option D correctly returns an object with update and destroy methods using concise method syntax. Option D is also valid JavaScript but less modern. Options B and C have syntax errors.

🧠 Conceptual

expert

How does Svelte use the return data from an action internally?

When a Svelte action returns an object with update and destroy methods, how does Svelte use these methods during the component lifecycle?

A Svelte calls <code>update</code> whenever the action's parameter changes and calls <code>destroy</code> when the element is removed from the DOM.

B Svelte calls <code>update</code> only once after the action is first applied and never calls <code>destroy</code>.

C Svelte calls <code>destroy</code> before calling <code>update</code> on every parameter change.

D Svelte ignores the returned object and manages the action lifecycle internally without calling these methods.

💡 Hint

Think about when parameters change and when elements are removed in Svelte.

Svelte calls the update method on the returned object whenever the action's parameter changes. It calls destroy when the element using the action is removed from the DOM to clean up.