Composable naming conventions (use prefix) in Vue - Performance & Optimization

Performance: Composable naming conventions (use prefix)

MEDIUM IMPACT

This affects code maintainability and load performance by enabling better tree-shaking and reducing unnecessary imports.

Organizing Vue composables for better performance and clarity

Vue

export function useData() { /* ... */ }
export function useUser() { /* ... */ }
export function useFetchData() { /* ... */ }

Consistent 'use' prefix signals composables clearly, enabling better tree-shaking and easier code understanding.

📈 Performance GainSaves KB in bundle size by excluding unused composables

Organizing Vue composables for better performance and clarity

Vue

export function useData() { /* ... */ }
export function useUser() { /* ... */ }
export function fetchData() { /* ... */ }

No consistent prefix makes it hard for bundlers to identify composables and may cause importing unnecessary code.

📉 Performance CostAdds extra KB to bundle due to less effective tree-shaking

Performance Comparison

Pattern	Bundle Size Impact	Tree-shaking Effectiveness	Load Time	Verdict
No prefix or inconsistent naming	Higher	Poor	Slower	[X] Bad
Consistent 'use' prefix for composables	Lower	Good	Faster	[OK] Good

Rendering Pipeline

Naming conventions do not directly affect rendering but influence bundle size and load time, which impacts the critical rendering path.

→Network

→Parse & Compile

→Script Execution

⚠️ BottleneckNetwork and Script Execution due to larger bundles

Optimization Tips

1Always prefix Vue composables with 'use' for clarity and performance.

2Consistent naming enables better tree-shaking and smaller bundles.

3Smaller bundles reduce script execution time and improve load speed.

Performance Quiz - 3 Questions

Why is using a consistent prefix like 'use' for Vue composables beneficial for performance?

A It helps bundlers identify and remove unused composables, reducing bundle size.

B It makes the code run faster in the browser by optimizing rendering.

C It automatically caches composable results to speed up UI updates.

D It reduces the number of DOM nodes created by the component.

DevTools: Network and Performance panels

How to check: Open DevTools, go to Network panel, reload page and check JS bundle sizes; then use Performance panel to measure script execution time.

What to look for: Smaller JS bundles and shorter script execution times indicate better composable naming and tree-shaking.

Practice

1. Why should composable functions in Vue start with the prefix use?

easy

A. To make them private and inaccessible outside the file

B. To make them run faster in the browser

C. To clearly indicate they are composables and follow Vue conventions

D. To prevent them from being imported accidentally

Solution

1. Step 1: Understand Vue composable naming conventions

   Vue recommends starting composable function names with use to clearly identify them as composables.

2. Step 2: Recognize the purpose of the prefix

   The prefix helps developers quickly know the function is a composable and follows community standards.

3. Final Answer:

   To clearly indicate they are composables and follow Vue conventions -> Option C

4. Quick Check:

   Composable prefix = use [OK]

Hint: Composable names start with 'use' to show their purpose [OK]

Common Mistakes:

• Thinking prefix affects performance
• Believing prefix hides the function
• Ignoring naming conventions

2. Which of the following is the correct syntax for naming a composable that fetches user data?

easy

A. useFetchUserData()

B. fetchUserData()

C. getUserData()

D. userDataFetch()

Solution

1. Step 1: Identify the composable prefix

   The composable should start with use to follow Vue naming conventions.

2. Step 2: Check the full function name

   useFetchUserData clearly shows it is a composable fetching user data.

3. Final Answer:

   useFetchUserData() -> Option A

4. Quick Check:

   Composable name starts with 'use' [OK]

Hint: Composable names always start with 'use' [OK]

Common Mistakes:

• Omitting the 'use' prefix
• Using verbs without 'use'
• Confusing composable with normal functions

3. Given this composable code:

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

What will be the output of console.log(counter.count.value) after calling counter.increment() twice?

medium

A. 1

B. 2

C. 0

D. undefined

Solution

1. Step 1: Understand the initial state

   The count ref starts at 0.

2. Step 2: Apply the increment function twice

   Each call to increment() increases count.value by 1, so after two calls, count.value is 2.

3. Final Answer:

   2 -> Option B

4. Quick Check:

   Increment twice = count 2 [OK]

Hint: Increment twice means count.value becomes 2 [OK]

Common Mistakes:

• Forgetting to access .value of ref
• Assuming count resets
• Confusing function call effects

4. Identify the error in this composable naming:

export function fetchData() {
  // composable logic
}

medium

A. Composable functions cannot be exported

B. Function should be a class, not a function

C. Function name is too long

D. Missing 'use' prefix in function name

Solution

1. Step 1: Check naming conventions for composables

   Composable functions must start with use to be recognized as such.

2. Step 2: Identify the missing prefix

   The function fetchData lacks the use prefix, so it breaks the convention.

3. Final Answer:

   Missing 'use' prefix in function name -> Option D

4. Quick Check:

   Composable names need 'use' prefix [OK]

Hint: Composable names must start with 'use' prefix [OK]

Common Mistakes:

• Ignoring naming conventions
• Thinking export is disallowed
• Confusing function types

5. You have multiple composables related to authentication: useAuthLogin, useAuthLogout, and useAuthStatus. Why is using the useAuth prefix a good practice?

hard

A. It groups related composables, making code easier to understand and maintain

B. It makes the composables run faster by grouping them

C. It hides the composables from other parts of the app

D. It automatically imports all composables with the prefix

Solution

1. Step 1: Understand prefix grouping purpose

   Using a common prefix groups related composables logically.

2. Step 2: Recognize benefits of grouping

   This grouping helps developers quickly find and understand related functions, improving maintainability.

3. Final Answer:

   It groups related composables, making code easier to understand and maintain -> Option A

4. Quick Check:

   Prefix groups related composables [OK]

Hint: Use prefixes to group related composables clearly [OK]

Common Mistakes:

• Assuming prefix affects performance
• Thinking prefix hides composables
• Believing prefix auto-imports functions