Dynamic components with is attribute in Vue - Performance & Optimization

Performance: Dynamic components with is attribute

MEDIUM IMPACT

This affects rendering speed and responsiveness by controlling which component Vue renders dynamically.

Switching between multiple components dynamically in Vue using the is attribute

Vue

<keep-alive>
  <component :is="currentComponent" />
</keep-alive>

// Keeps inactive components cached to avoid full reloads

Caching inactive components avoids destroying and recreating them, reducing reflows and improving responsiveness.

📈 Performance GainReduces reflows to zero on cached switches, improving INP by 30-50ms on average

Switching between multiple components dynamically in Vue using the is attribute

Vue

<component :is="currentComponent" />

// currentComponent changes frequently triggering full component reloads

Each change destroys the old component and creates a new one, causing full re-renders and layout recalculations.

📉 Performance CostTriggers 1 full reflow and repaint per component switch, blocking interaction for 50-100ms on complex components

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Dynamic component switch without caching	Destroys and recreates full component subtree	1 reflow per switch	High paint cost due to full redraw	[X] Bad
Dynamic component switch with <keep-alive>	Reuses cached DOM nodes, minimal DOM changes	No reflows on cached switches	Low paint cost, only updates needed	[OK] Good

Rendering Pipeline

When the is attribute changes, Vue destroys the old component and creates a new one, triggering style recalculation, layout, paint, and composite stages.

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckLayout and Paint stages are most expensive due to full component teardown and rebuild.

Core Web Vital Affected

INP

This affects rendering speed and responsiveness by controlling which component Vue renders dynamically.

Optimization Tips

1Avoid frequent full component destruction when switching dynamic components.

2Use <keep-alive> to cache components and reduce reflows and repaints.

3Monitor Layout and Paint times in DevTools Performance panel to detect costly re-renders.

Performance Quiz - 3 Questions

What is the main performance cost when switching dynamic components using the is attribute without caching?

A No DOM changes, just attribute updates

B Full component destruction and recreation causing reflows and repaints

C Only style recalculation without layout changes

D Network delay fetching new component code

DevTools: Performance

How to check: Record a performance profile while switching dynamic components. Look for Layout and Paint events after each switch.

What to look for: High Layout and Paint times indicate full re-renders. Lower times with <keep-alive> show better performance.

Practice

1. What does the is attribute do in Vue's <component> tag?

easy

A. It binds data to the component's props.

B. It sets the CSS style of the component.

C. It tells Vue which component to render dynamically.

D. It triggers a lifecycle hook in the component.

Solution

1. Step 1: Understand the role of <component> tag

   The <component> tag in Vue is a special tag used to render different components dynamically.

2. Step 2: Identify the purpose of the is attribute

   The is attribute specifies which component to render by binding to a variable or string representing the component name.

3. Final Answer:

   It tells Vue which component to render dynamically. -> Option C

4. Quick Check:

   Dynamic component selection = is attribute [OK]

Hint: Remember: picks component x [OK]

Common Mistakes:

• Thinking is sets styles
• Confusing is with prop binding
• Assuming is triggers lifecycle hooks

2. Which of the following is the correct syntax to use a dynamic component named MyButton in Vue?

easy

A.

B.

C.

D.

Solution

1. Step 1: Understand binding syntax for dynamic components

   The is attribute must be bound with : to a variable or string. To specify a component by name as a string, use quotes inside the binding.

2. Step 2: Check each option's syntax

   uses is="MyButton" without binding, so Vue treats it as a literal tag, not a component name. binds MyButton as a variable, but if MyButton is not defined in the script, it fails. correctly binds is to the string 'MyButton'. uses is='MyButton' without binding, which is invalid for dynamic components.

3. Final Answer:

   <component :is='"MyButton"'></component> -> Option A

4. Quick Check:

   Use :is with quotes for string component names [OK]

Hint: Use :is with quotes for string names, no quotes without : [OK]

Common Mistakes:

• Omitting the colon for binding
• Using quotes without binding
• Binding to undefined variables

3. Given the Vue template:

<template>
  <component :is="currentView" />
</template>

<script setup>
import HomeView from './HomeView.vue'
import AboutView from './AboutView.vue'

const currentView = ref('HomeView')
</script>

What will be rendered initially?

medium

A. The HomeView component

B. The AboutView component

C. A runtime error because currentView is a string

D. An empty component (nothing rendered)

Solution

1. Step 1: Analyze the value of currentView

   The variable currentView is a ref holding the string 'HomeView'.

2. Step 2: Understand how Vue resolves dynamic components

   Vue expects the is attribute to be a component object or a registered component name. Here, 'HomeView' is a string but the component is imported as HomeView object, not registered globally or locally by that string name.

3. Step 3: Result of passing string without registration

   Since 'HomeView' is not registered as a component name, Vue renders nothing (empty component) without error.

4. Final Answer:

   An empty component (nothing rendered) -> Option D

5. Quick Check:

   Unregistered string name = empty render [OK]

Hint: Dynamic component string must be registered or component object [OK]

Common Mistakes:

• Assuming string name auto-resolves to imported component
• Expecting runtime error for string value
• Confusing ref value with component object

4. Identify the error in this Vue code snippet:

<template>
  <component :is="currentComp" />
</template>

<script setup>
import Foo from './Foo.vue'

const currentComp = Foo
</script>

medium

A. No error; this code works correctly

B. The currentComp variable should be a string, not a component object

C. Missing quotes around component name in is attribute

D. The component tag must be self-closing with a closing slash

Solution

1. Step 1: Check the type of currentComp

   currentComp is assigned the imported component object Foo, which is valid for dynamic components.

2. Step 2: Verify the component tag usage

   The <component> tag uses :is="currentComp" correctly, and self-closing syntax is allowed in Vue templates.

3. Final Answer:

   No error; this code works correctly -> Option A

4. Quick Check:

   Passing component object to :is works fine [OK]

Hint: Pass component objects directly to :is for dynamic rendering [OK]

Common Mistakes:

• Thinking :is must always be a string
• Confusing self-closing tags as errors
• Expecting quotes around component objects

5. You want to switch between three components HomeView, ProfileView, and SettingsView dynamically based on a button click. Which approach correctly implements this using Vue's dynamic components?

hard

A. <template>
<component :is="currentView" />
<button @click="currentView = 'HomeView'">Home</button>
<button @click="currentView = 'ProfileView'">Profile</button>
<button @click="currentView = 'SettingsView'">Settings</button>
</template>

<script setup>
import HomeView from './HomeView.vue'
import ProfileView from './ProfileView.vue'
import SettingsView from './SettingsView.vue'

const currentView = ref(HomeView)
</script>

B. <template>
<component :is="currentView" />
<button @click="currentView = HomeView">Home</button>
<button @click="currentView = ProfileView">Profile</button>
<button @click="currentView = SettingsView">Settings</button>
</template>

<script setup>
import HomeView from './HomeView.vue'
import ProfileView from './ProfileView.vue'
import SettingsView from './SettingsView.vue'

const currentView = ref(HomeView)
</script>

C. <template>
<component :is="currentView" />
<button @click="currentView = 'HomeView'">Home</button>
<button @click="currentView = 'ProfileView'">Profile</button>
<button @click="currentView = 'SettingsView'">Settings</button>
</template>

<script setup>
import HomeView from './HomeView.vue'
import ProfileView from './ProfileView.vue'
import SettingsView from './SettingsView.vue'

const currentView = ref('HomeView')
</script>

D. <template>
<component :is="currentView" />
<button @click="currentView = HomeView">Home</button>
<button @click="currentView = ProfileView">Profile</button>
<button @click="currentView = SettingsView">Settings</button>
</template>

<script setup>
import HomeView from './HomeView.vue'
import ProfileView from './ProfileView.vue'
import SettingsView from './SettingsView.vue'

const currentView = ref('HomeView')
</script>

Solution

1. Step 1: Understand how to switch components dynamically

   To switch components dynamically, currentView must hold the component object, not a string, unless the string matches a registered component name.

2. Step 2: Analyze each option's approach

   <template>
     <component :is="currentView" />
     <button @click="currentView = 'HomeView'">Home</button>
     <button @click="currentView = 'ProfileView'">Profile</button>
     <button @click="currentView = 'SettingsView'">Settings</button>
   </template>
   
   <script setup>
   import HomeView from './HomeView.vue'
   import ProfileView from './ProfileView.vue'
   import SettingsView from './SettingsView.vue'
   
   const currentView = ref(HomeView)
   </script>

   initializes currentView with a component object but sets it to strings on button clicks, causing mismatch.

   <template>
     <component :is="currentView" />
     <button @click="currentView = HomeView">Home</button>
     <button @click="currentView = ProfileView">Profile</button>
     <button @click="currentView = SettingsView">Settings</button>
   </template>
   
   <script setup>
   import HomeView from './HomeView.vue'
   import ProfileView from './ProfileView.vue'
   import SettingsView from './SettingsView.vue'
   
   const currentView = ref(HomeView)
   </script>

   initializes and updates currentView with component objects consistently, which is correct.

   <template>
     <component :is="currentView" />
     <button @click="currentView = 'HomeView'">Home</button>
     <button @click="currentView = 'ProfileView'">Profile</button>
     <button @click="currentView = 'SettingsView'">Settings</button>
   </template>
   
   <script setup>
   import HomeView from './HomeView.vue'
   import ProfileView from './ProfileView.vue'
   import SettingsView from './SettingsView.vue'
   
   const currentView = ref('HomeView')
   </script>

   uses strings only, but these strings are not registered component names, so Vue won't render them.

   <template>
     <component :is="currentView" />
     <button @click="currentView = HomeView">Home</button>
     <button @click="currentView = ProfileView">Profile</button>
     <button @click="currentView = SettingsView">Settings</button>
   </template>
   
   <script setup>
   import HomeView from './HomeView.vue'
   import ProfileView from './ProfileView.vue'
   import SettingsView from './SettingsView.vue'
   
   const currentView = ref('HomeView')
   </script>

   mixes component objects and strings inconsistently, causing errors.

3. Final Answer:

   Option B correctly uses component objects for dynamic switching. -> Option B

4. Quick Check:

   Use component objects consistently for :is switching [OK]

Hint: Keep :is value consistent: all component objects or all registered strings [OK]

Common Mistakes:

• Mixing strings and component objects in :is
• Using unregistered string names
• Initializing with object but switching to strings