Why composables matter in Vue - Visual Breakdown

Concept Flow - Why composables matter

Start: Need reusable logic

↓

Create composable function

↓

Use composable in components

↓

Share state and behavior

↓

Simplify components

↓

Easier testing and maintenance

↓

End

This flow shows how composables help by extracting reusable logic into functions that components can share, making code simpler and easier to maintain.

Execution Sample

Vue

import { ref } from 'vue'

export function useCounter() {
  const count = ref(0)
  function increment() {
    count.value++
  }
  return { count, increment }
}

This composable provides a counter state and an increment function to be reused in multiple components.

Execution Table

Step	Action	State Before	State After	Output/Effect
1	Call useCounter()	No count	count = 0	Composable initialized with count 0
2	Call increment()	count = 0	count = 1	Count increased to 1
3	Call increment()	count = 1	count = 2	Count increased to 2
4	Return { count, increment }	count = 2	count = 2	Composable returns reactive state and function
5	Component uses composable	No local count	count reactive linked	Component can display and update count
6	Another component calls useCounter()	No count	count = 0	New independent count state created
7	Call increment() in second component	count = 0	count = 1	Second component count increases independently

💡 Execution stops after composable returns and components use independent reactive states.

Variable Tracker

Variable	Start	After 1	After 2	After 3	Final
count (first composable)	undefined	0	1	2	2
count (second composable)	undefined	0	0	1	1

Key Moments - 2 Insights

Why does each component get its own count value when using the same composable?

Because the composable function creates a new reactive count variable each time it is called, as shown in execution_table rows 1 and 6.

What happens if we don't return the count and increment from the composable?

The component cannot access or update the count state, so the composable would not be useful. See execution_table row 4 where the return enables usage.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what is the value of count after increment() is called the second time?

A 2

B 0

C 1

D 3

💡 Hint

Check the 'State After' column in execution_table row 3.

At which step does the second component get its own independent count state?

A Step 2

B Step 6

C Step 5

D Step 7

💡 Hint

Look for when useCounter() is called again for a new component in execution_table.

If the composable did not return the increment function, what would happen in the component?

A count would not be reactive

B Component could still update count directly

C Component could not update count

D Component would get an error immediately

💡 Hint

Refer to execution_table row 4 about what is returned from the composable.

Concept Snapshot

Why Composables Matter in Vue:
- Composables are functions that hold reusable reactive logic.
- Each call creates independent reactive state.
- Components use composables to share behavior simply.
- Returning state and functions enables interaction.
- They simplify code and improve maintainability.

Full Transcript

Composables in Vue are special functions that let you reuse reactive logic across components. When you call a composable, it creates its own reactive state, like a counter starting at zero. You can then use functions it returns to update that state. Each component calling the composable gets its own separate state, so they don't interfere. This helps keep components simple and makes code easier to maintain and test. The example shows a useCounter composable that returns a count and an increment function. Calling increment increases the count. Components use this composable to share the counting logic without repeating code.