Global properties and methods in Vue - Performance & Optimization

Performance: Global properties and methods

MEDIUM IMPACT

Global properties and methods affect initial app load and runtime performance by adding shared reactive or non-reactive data accessible across components.

Sharing utility functions or data across many Vue components

Vue

import { heavyFunction } from './utils';
// Use heavyFunction only where needed inside components

Imports keep code split and only load functions when components use them, reducing global overhead.

📈 Performance Gainreduces bundle size by 50kb+, lowers memory use, improves interaction speed

Sharing utility functions or data across many Vue components

Vue

app.config.globalProperties.$utils = { heavyFunction: () => { /* large code */ } }

Attaching large or complex objects to globalProperties increases bundle size and runtime memory usage, slowing interaction responsiveness.

📉 Performance Costadds 50kb+ to bundle, increases memory usage, may block rendering for 20ms+

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Large globalProperties object	0 (no DOM changes)	0	0	[!] OK but costly in JS execution and memory
Scoped imports in components	0	0	0	[OK] Minimal JS overhead, better load performance

Rendering Pipeline

Global properties are set during app initialization and accessed during component render and updates. They affect JavaScript execution and reactive dependency tracking.

→JavaScript Execution

→Reactive Dependency Tracking

→Component Render

⚠️ BottleneckJavaScript Execution when large global objects are created or accessed frequently

Core Web Vital Affected

INP

Global properties and methods affect initial app load and runtime performance by adding shared reactive or non-reactive data accessible across components.

Optimization Tips

1Avoid adding large objects or heavy functions to globalProperties.

2Import utilities in components instead of using globalProperties when possible.

3Limit globalProperties to small, essential shared data to reduce runtime overhead.

Performance Quiz - 3 Questions

What is a performance risk of adding large objects to Vue's globalProperties?

A Improves Largest Contentful Paint (LCP)

B Increases bundle size and runtime memory usage

C Causes more DOM reflows

D Reduces JavaScript execution time

DevTools: Performance

How to check: Record a performance profile during app startup and interaction; look for long scripting tasks related to globalProperties initialization or usage.

What to look for: Long scripting blocks or high memory usage indicating heavy global properties slowing interaction responsiveness

Practice

1. What is the main purpose of app.config.globalProperties in Vue?

easy

A. To add properties or methods accessible in all components

B. To register new components globally

C. To configure routing paths

D. To define component-specific data

Solution

1. Step 1: Understand the role of app.config.globalProperties

   This object allows adding properties or methods that every Vue component can access easily.

2. Step 2: Differentiate from other Vue features

   Registering components, routing, and component data are handled differently, not via globalProperties.

3. Final Answer:

   To add properties or methods accessible in all components -> Option A

4. Quick Check:

   Global properties = shared access across components [OK]

Hint: Global properties share code across all components [OK]

Common Mistakes:

• Confusing globalProperties with component registration
• Thinking it configures routing
• Assuming it stores component local data

2. Which of the following is the correct way to add a global method named logMessage in Vue 3?

easy

A. app.globalProperties.logMessage = () => console.log('Hi')

B. app.config.globalProperties.logMessage = function logMessage() { console.log('Hi') }

C. app.config.globalProperties.logMessage = () => console.log('Hi')

D. app.config.globalProperties.$logMessage = () => console.log('Hi')

Solution

1. Step 1: Recall the correct syntax for global properties

   Global properties must be added to app.config.globalProperties with a $ prefix on the property name.

2. Step 2: Check the options for correct prefix and assignment

   app.config.globalProperties.$logMessage = () => console.log('Hi') correctly uses app.config.globalProperties.$logMessage with an arrow function.

3. Final Answer:

   app.config.globalProperties.$logMessage = () => console.log('Hi') -> Option D

4. Quick Check:

   Use app.config.globalProperties.$name for globals [OK]

Hint: Global properties need $ prefix and app.config [OK]

Common Mistakes:

• Omitting the $ prefix
• Using app.globalProperties instead of app.config.globalProperties
• Assigning without a function

3. Given this setup in main.js:

app.config.globalProperties.$greet = (name) => `Hello, ${name}!`

What will be the output of this code inside a component method?

console.log(this.$greet('Alice'))

medium

A. undefined

B. Hello, Alice!

C. Error: $greet is not a function

D. Hello, ${name}!

Solution

1. Step 1: Understand the global method definition

   The method $greet is defined globally to return a greeting string with the passed name.

2. Step 2: Analyze the component call

   Calling this.$greet('Alice') invokes the global method, returning Hello, Alice!.

3. Final Answer:

   Hello, Alice! -> Option B

4. Quick Check:

   Global method call returns expected string [OK]

Hint: Global methods run with this.$name inside components [OK]

Common Mistakes:

• Expecting template literal without interpolation
• Forgetting to use this.$ prefix
• Assuming method is undefined

4. Identify the error in this Vue 3 global property setup:

app.config.globalProperties.log = function(message) {
  console.log(message)
}

// Usage in component:
this.$log('Test')

medium

A. Missing $ prefix in global property name

B. Function syntax is incorrect

C. Cannot use global properties inside components

D. Should use arrow function instead of regular function

Solution

1. Step 1: Check the global property name

   The property is named log but used as $log in the component, causing mismatch.

2. Step 2: Understand Vue global property naming convention

   Global properties must be defined with a $ prefix to match usage in components.

3. Final Answer:

   Missing $ prefix in global property name -> Option A

4. Quick Check:

   Global properties need $ prefix to match usage [OK]

Hint: Global property name and usage must both have $ prefix [OK]

Common Mistakes:

• Defining without $ but using with $
• Thinking function syntax is wrong
• Believing global properties can't be used in components

5. You want to create a global property $formatDate that formats a Date object to YYYY-MM-DD. Which is the best way to define and use it in Vue 3?

hard

A. Add a global variable formatDate in main.js and use formatDate(date) in components

B. Create a component method named formatDate and call this.formatDate(date)

C. Define in app.config.globalProperties.$formatDate as a function returning formatted string; call with this.$formatDate(date) in components

D. Use a computed property in each component to format dates

Solution

1. Step 1: Understand global property usage

   Global properties are added to app.config.globalProperties with a $ prefix and accessed via this.$name in components.

2. Step 2: Evaluate options for best practice

   Define in app.config.globalProperties.$formatDate as a function returning formatted string; call with this.$formatDate(date) in components correctly defines the formatter globally and uses it properly in components, promoting code reuse.

3. Final Answer:

   Define in app.config.globalProperties.$formatDate as a function returning formatted string; call with this.$formatDate(date) in components -> Option C

4. Quick Check:

   Global reusable methods use $ prefix and app.config [OK]

Hint: Use app.config.globalProperties with $ prefix for reusable methods [OK]

Common Mistakes:

• Defining methods only inside components losing reuse
• Using global variables without Vue context
• Not using $ prefix for global properties