Action with event dispatching in Svelte - Step-by-Step Execution

Concept Flow - Action with event dispatching

Component mounts

↓

Action initialized

↓

User event triggers action

↓

Action dispatches custom event

↓

Component listens and handles event

↓

Component updates state/UI

This flow shows how a Svelte action attaches to an element, listens for user events, dispatches a custom event, and the component reacts to update UI.

Execution Sample

Svelte

function myAction(node) {
  const handleClick = () => {
    node.dispatchEvent(new CustomEvent('myEvent'));
  };
  node.addEventListener('click', handleClick);
  return { destroy() { node.removeEventListener('click', handleClick); } };
}

This Svelte action listens for clicks on an element and dispatches a custom event 'myEvent' when clicked.

Execution Table

Step	Action	Event Listener Added	Event Triggered	Custom Event Dispatched	Component Reaction
1	Component mounts and action attaches	click listener added to node	No	No	No
2	User clicks element	click listener active	Yes	Yes: 'myEvent'	Component catches 'myEvent'
3	Component updates state/UI based on event	listener still active	No	No	UI updates accordingly
4	Component unmounts or action removed	click listener removed	No	No	No further reactions

💡 Action cleans up event listener when component unmounts or action is destroyed

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
node	DOM element reference	Listener attached	Listener active	Listener active	Listener removed
handleClick	Function defined	Registered as listener	Called on click	Not called	Removed

Key Moments - 2 Insights

Why does the custom event 'myEvent' need to be dispatched inside the action?

Because the action controls the element's behavior and dispatching the event inside it lets the component listen and react to user interactions, as shown in execution_table step 2.

What happens if the event listener is not removed when the component unmounts?

The listener stays active causing potential memory leaks or unexpected behavior. Execution_table step 4 shows the cleanup removing the listener.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the custom event 'myEvent' dispatched?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Check the 'Custom Event Dispatched' column in execution_table

According to variable_tracker, what happens to the 'handleClick' function after step 4?

A It is called repeatedly

B It is removed as listener

C It remains registered as listener

D It dispatches more events

💡 Hint

Look at the 'handleClick' row under 'Final' column in variable_tracker

If the user never clicks the element, which steps in execution_table will occur?

A Steps 1 and 4 only

B Steps 1, 2, and 3

C All steps

D Only step 2

💡 Hint

Refer to 'Event Triggered' column to see when user clicks happen

Concept Snapshot

Svelte actions attach behavior to elements.
They can listen for events and dispatch custom events.
Components listen to these custom events to update UI.
Always clean up event listeners in action's destroy.
Use node.dispatchEvent(new CustomEvent('name')) inside action.

Full Transcript

In Svelte, an action is a function that attaches to a DOM element when the component mounts. This action can add event listeners to the element, such as listening for clicks. When the user clicks the element, the action dispatches a custom event using node.dispatchEvent with a CustomEvent. The component listens for this custom event and updates its state or UI accordingly. When the component unmounts or the action is removed, the event listener is cleaned up to avoid memory leaks. This flow ensures interactive behavior is encapsulated in the action and the component reacts to events cleanly.