Component registration (global vs local) in Vue - Visual Side-by-Side Comparison

Concept Flow - Component registration (global vs local)

Define Component

↓

Register Globally

↓

Available in All Components

↓

Register Locally

↓

Available Only in Parent Component

This flow shows how a component is defined and then registered either globally for all components or locally for just one parent component.

Execution Sample

Vue

import MyButton from './MyButton.vue'

// Global registration
app.component('MyButton', MyButton)

// Local registration
export default {
  components: { MyButton }
}

This code shows importing a component and registering it globally on the app or locally inside a component.

Execution Table

Step	Action	Registration Type	Scope	Result
1	Import MyButton component	N/A	N/A	MyButton component loaded
2	Register MyButton globally on app	Global	All components	MyButton usable anywhere in app
3	Define ParentComponent with local registration	Local	ParentComponent only	MyButton locally registered in ParentComponent
4	Use MyButton in ChildComponent without local registration	Global	All components	MyButton renders correctly
5	Use MyButton in ParentComponent	Local	ParentComponent only	MyButton renders correctly
6	Use MyButton in any component after global registration	Global	All components	MyButton renders correctly
7	Exit	N/A	N/A	Component registration scope determined

💡 Component registration scope defines where the component can be used; global means everywhere, local means only in the registering component.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 6
MyButton availability	Not loaded	Available globally	Available globally and locally in ParentComponent	Available globally

Key Moments - 2 Insights

Why does MyButton work in ParentComponent but not in ChildComponent when registered locally?

Because local registration only makes the component available inside the registering component (ParentComponent). ChildComponent does not see it unless it also registers it or global registration is used (see execution_table rows 3 and 4).

What happens if you register a component both globally and locally?

The local registration takes precedence inside that component, but effectively the component is available everywhere due to global registration (see execution_table rows 2 and 3).

Visual Quiz - 3 Questions

Look at the execution table, at which step is MyButton made available to all components?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Check the 'Registration Type' and 'Scope' columns in execution_table row 2.

According to the variable tracker, what is the availability of MyButton after step 3?

A Available locally in ParentComponent

B Available globally

C Not loaded

D Unavailable

💡 Hint

Look at the 'After Step 3' column for 'MyButton availability' in variable_tracker.

If you remove the global registration at step 2, what will happen when ChildComponent tries to use MyButton?

A It will cause an error

B It will render correctly

C It will render but with warnings

D It will render only if ParentComponent is its parent

💡 Hint

Local registration (step 3) does not make MyButton available to ChildComponent; it requires its own registration or global registration.

Concept Snapshot

Component registration in Vue:
- Global registration: app.component('Name', Component) makes it usable everywhere.
- Local registration: components: { Name } makes it usable only inside that component.
- Local overrides global inside that component.
- Use global for shared components, local for isolated use.
- Missing registration causes 'component not found' errors.

Full Transcript

This lesson shows how Vue components can be registered globally or locally. Global registration makes a component available in all parts of the app. Local registration limits usage to the component that registers it. The execution table traces importing a component, registering it globally, then locally inside a parent component. It shows that a child component without registration cannot use the locally registered component. The variable tracker follows the availability of the component through these steps. Key moments clarify why local registration limits scope and how global registration affects availability. The quiz tests understanding of when and where the component is usable. The snapshot summarizes the main points for quick review.

Practice

1. What is the main difference between global and local component registration in Vue?

easy

A. Global registration requires importing components manually, local does not.

B. Local registration makes a component available everywhere, global limits it to one component.

C. Global registration makes a component available everywhere, local limits it to one component.

D. Local registration automatically registers components globally.

Solution

1. Step 1: Understand global registration

   Global registration means the component can be used in any template without importing it again.

2. Step 2: Understand local registration

   Local registration means the component is only available inside the component where it is registered.

3. Final Answer:

   Global registration makes a component available everywhere, local limits it to one component. -> Option C

4. Quick Check:

   Global = everywhere, Local = one component [OK]

Hint: Global = everywhere, local = one place only [OK]

Common Mistakes:

• Confusing global with local availability
• Thinking local registration is automatic
• Assuming global requires manual import every time

2. Which of the following is the correct syntax to register a component locally inside a Vue component?

easy

A. export default { globalComponents: { MyComponent } }

B. Vue.component('MyComponent', MyComponent)

C. import MyComponent from './MyComponent.vue';

D. components: { MyComponent }

Solution

1. Step 1: Identify local registration syntax

   Local registration uses the components option inside the component definition object.

2. Step 2: Match correct syntax

   The syntax is components: { MyComponent } to register locally.

3. Final Answer:

   components: { MyComponent } -> Option D

4. Quick Check:

   Local registration uses components: { } [OK]

Hint: Local registration uses components: { ComponentName } [OK]

Common Mistakes:

• Using Vue.component() for local registration
• Confusing import statement with registration
• Trying to use globalComponents option which doesn't exist

3. Given this code, what will be the output when rendering <ParentComponent/>?

const ChildComponent = {
  template: '
Child here
'
}

const ParentComponent = {
  template: '
',
  components: { ChildComponent }
}

app.component('parent-component', ParentComponent)
app.mount('#app')

medium

A. Child here

B. Error: Unknown custom element

C.

D. Child here

Solution

1. Step 1: Check local registration in ParentComponent

   ChildComponent is registered locally inside ParentComponent using components: { ChildComponent }.

2. Step 2: Understand template rendering

   The tag inside ParentComponent's template will render ChildComponent's template

   Child here

   only if the tag name matches the registered component name in kebab-case.

3. Step 3: Identify the issue

   The component is registered as ChildComponent but used as , which Vue treats as a different tag. Since 'child-component' is not globally registered, Vue will throw an unknown custom element error.

4. Final Answer:

   Error: Unknown custom element <child-component> -> Option B

5. Quick Check:

   Component names are case-sensitive and must match usage [OK]

Hint: Component names must match tag names exactly or use kebab-case [OK]

Common Mistakes:

• Assuming PascalCase component names automatically match kebab-case tags
• Forgetting to register components globally when using kebab-case tags
• Expecting local registration to work with mismatched tag names

4. What is wrong with this Vue code snippet?

const app = Vue.createApp({})

app.component('MyButton', {
  template: 'Click me'
})

const AnotherComponent = {
  template: ''
}

app.component('AnotherComponent', AnotherComponent)

app.mount('#app')

medium

A. The tag inside AnotherComponent template should be lowercase .

B. MyButton component is not registered globally.

C. AnotherComponent is missing local registration of MyButton.

D. Vue.createApp() cannot register components.

Solution

1. Step 1: Check component registration

   MyButton is registered globally using app.component('MyButton', ...), so it is available everywhere.

2. Step 2: Check template tag casing

   Vue requires component tags in templates to be kebab-case or PascalCase but HTML is case-insensitive, so should be .

3. Final Answer:

   The <MyButton /> tag inside AnotherComponent template should be lowercase <my-button />. -> Option A

4. Quick Check:

   Component tags must be kebab-case in templates [OK]

Hint: Use kebab-case for component tags in templates [OK]

Common Mistakes:

• Using PascalCase tags directly in templates
• Thinking global registration needs import in every component
• Assuming Vue.createApp() can't register components

5. You have a button component used in many places and a modal component used only inside one page component. How should you register them for best practice?

hard

A. Register the button component globally and the modal component locally inside the page component.

B. Register both components globally for consistency.

C. Register both components locally inside each component that uses them.

D. Register the modal component globally and the button component locally.

Solution

1. Step 1: Consider usage frequency

   The button is used many places, so global registration avoids repeated imports and registrations.

2. Step 2: Consider component scope

   The modal is used only inside one page component, so local registration keeps scope limited and reduces global clutter.

3. Final Answer:

   Register the button component globally and the modal component locally inside the page component. -> Option A

4. Quick Check:

   Global for many uses, local for few uses [OK]

Hint: Global for shared, local for limited use components [OK]

Common Mistakes:

• Registering rarely used components globally unnecessarily
• Registering widely used components locally repeatedly
• Ignoring app size and performance considerations