Renderless components in Vue - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What does this renderless component output?

Consider this Vue 3 renderless component using the Composition API. What will be rendered in the parent component?

Vue

<template>
  <slot :count="count" />
</template>

<script setup>
import { ref } from 'vue'
const count = ref(0)
setInterval(() => { count.value++ }, 1000)
</script>

A <p>Nothing visible, only slot content with count prop updates</p>

B <p>Displays the number 0 only once</p>

C <p>Shows a static text 'count' without numbers</p>

D <p>Throws an error because count is not reactive</p>

💡 Hint

Think about what a renderless component does with slots and reactive data.

The component itself renders nothing except the slot. The slot receives the reactive count prop, so the parent can display it. The component does not render any visible output by itself.

❓ state_output

intermediate

What is the value of count after 3 seconds?

Given this renderless component code, what will be the value of count after 3 seconds?

Vue

<script setup>
import { ref } from 'vue'
const count = ref(0)
setInterval(() => { count.value++ }, 1000)
</script>

A 2

B 0

C Undefined

D 3

💡 Hint

Count increments every 1000 milliseconds starting from 0.

The setInterval runs every 1 second, increasing count by 1. After 3 seconds, count will be 3.

📝 Syntax

advanced

Which option correctly passes reactive data to a slot in a renderless component?

Identify the correct syntax to pass reactive count to a default slot in a renderless component.

Vue

<template>
  <!-- Choose the correct slot binding -->
</template>

<script setup>
import { ref } from 'vue'
const count = ref(0)
</script>

A <slot :count="count" />

B <slot count="count" />

C <slot :count="count.value" />

D <slot v-bind:count="count" />

💡 Hint

Remember how to bind reactive refs to slots in Vue 3.

Using :count="count" passes the reactive ref itself, allowing the parent to access count.value. Passing count.value directly would pass a primitive, losing reactivity.

🔧 Debug

advanced

Why does this renderless component not update the slot content?

This renderless component passes count to a slot, but the parent does not see updates. Why?

Vue

<template>
  <slot :count="count" />
</template>

<script setup>
import { ref } from 'vue'
const count = 0
setInterval(() => { count++ }, 1000)
</script>

A Because setInterval is not inside onMounted lifecycle hook

B Because the slot is missing a name attribute

C Because count is a plain number, not reactive, so updates don't trigger re-render

D Because the component template is missing a root element

💡 Hint

Check how count is declared and updated.

count is a plain number, not a reactive ref. Incrementing it does not notify Vue to update the slot content. Using ref(0) makes it reactive.

🧠 Conceptual

expert

What is the main advantage of using renderless components in Vue?

Choose the best explanation for why developers use renderless components.

A They improve performance by rendering nothing and skipping reactivity

B They separate logic from UI, allowing flexible rendering by the parent component

C They enforce strict styling rules by hiding all HTML elements

D They automatically generate UI elements based on data without slots

💡 Hint

Think about how renderless components help reuse logic.

Renderless components provide reusable logic and state but delegate rendering to the parent via slots. This allows flexible UI design while sharing behavior.

Practice

1. What is the main purpose of a renderless component in Vue?

easy

A. To share logic without rendering any UI elements

B. To render a default UI for all child components

C. To replace the Vue router for navigation

D. To automatically fetch data from APIs

Solution

1. Step 1: Understand the concept of renderless components

   Renderless components are designed to provide reusable logic without producing any visible UI themselves.

2. Step 2: Compare options with the concept

   Options A, B, and D describe unrelated Vue features or behaviors. Only To share logic without rendering any UI elements correctly describes the purpose of renderless components.

3. Final Answer:

   To share logic without rendering any UI elements -> Option A

4. Quick Check:

   Renderless components = share logic only [OK]

Hint: Renderless means no UI, just logic sharing [OK]

Common Mistakes:

• Thinking renderless components render UI
• Confusing with routing or data fetching
• Assuming they provide default templates

2. Which syntax correctly defines a renderless component using slots in Vue 3?

easy

A. <template><slot :data="someData" /></template>

B. <template><div>Hello</div></template>

C. <script>export default { render() { return null } }</script>

D. <template><button>Click</button></template>

Solution

1. Step 1: Identify renderless component pattern

   Renderless components use slots to pass data and methods without rendering UI elements themselves.

2. Step 2: Analyze each option

   <template><slot :data="someData" /></template> uses a slot with a prop to pass data, which is the correct renderless pattern. Options A and D render UI elements, and C returns null but does not use slots.

3. Final Answer:

   <template><slot :data="someData" /></template> -> Option A

4. Quick Check:

   Renderless = slot with data prop [OK]

Hint: Renderless components pass data via slots, no UI tags [OK]

Common Mistakes:

• Including UI elements inside renderless components
• Not using slots to expose data
• Returning null without slots

3. Given this renderless component usage:

<RenderlessCounter v-slot="{ count, increment }">
  <button @click="increment">Count: {{ count }}</button>
</RenderlessCounter>

What will happen when the button is clicked?

medium

A. The button resets the count to zero

B. Nothing happens because the component does not render UI

C. An error occurs because increment is not defined

D. The count value increases and the button text updates

Solution

1. Step 1: Understand slot props usage

   The renderless component exposes count and increment via slot props, which the parent uses to render a button and handle clicks.

2. Step 2: Analyze button click effect

   Clicking the button calls increment, which increases count. The button text updates because it uses {{ count }}.

3. Final Answer:

   The count value increases and the button text updates -> Option D

4. Quick Check:

   Slot props update UI on click [OK]

Hint: Slot props provide data and methods to parent [OK]

Common Mistakes:

• Assuming renderless means no UI updates
• Thinking increment is undefined
• Confusing renderless with no interaction

4. Identify the error in this renderless component definition:

<template>
  <slot>Default</slot>
</template>

<script setup>
import { ref } from 'vue'
const count = ref(0)
function increment() {
  count++
}
</script>

medium

A. Template must have a root element wrapping slot

B. Slot usage is invalid without a name

C. Increment function incorrectly updates count with count++ instead of count.value++

D. Ref is not imported from Vue

Solution

1. Step 1: Check reactive ref usage

   In Vue 3, refs must be updated via count.value++, not count++.

2. Step 2: Verify other parts

   Slot usage without a name is valid for default slot. Template can have a single root slot. Ref is properly imported from Vue.

3. Final Answer:

   Increment function incorrectly updates count with count++ instead of count.value++ -> Option C

4. Quick Check:

   Update ref with .value [OK]

Hint: Use .value to update refs in Vue 3 [OK]

Common Mistakes:

• Updating ref directly without .value
• Assuming slot needs a name
• Thinking template must wrap slot in div

5. You want to create a renderless component that tracks mouse position and shares it with any parent component. Which approach correctly implements this?

hard

A. <template><div>Mouse at {{ x }}, {{ y }}</div></template>

<script setup>
const x = ref(0)
const y = ref(0)
window.addEventListener('mousemove', e => {
x.value = e.clientX
y.value = e.clientY
})
</script>

B. <template><slot :pos="position" /></template>

<script setup>
import { reactive } from 'vue'
const position = reactive({ x: 0, y: 0 })
window.addEventListener('mousemove', e => {
position.x = e.clientX
position.y = e.clientY
})
</script>

C. <template><slot /></template>

<script setup>
import { reactive } from 'vue'
const position = reactive({ x: 0, y: 0 })
window.addEventListener('mousemove', e => {
position.x = e.clientX
position.y = e.clientY
})
</script>

D. <template><slot :x="x" :y="y" /></template>

<script setup>
let x = 0
let y = 0
window.addEventListener('mousemove', e => {
x = e.clientX
y = e.clientY
})
</script>

Solution

1. Step 1: Identify renderless component pattern

   The component must not render UI but expose reactive data via slot props.

2. Step 2: Analyze each option for correctness

   <template><slot :x="x" :y="y" /></template> <script setup> let x = 0 let y = 0 window.addEventListener('mousemove', e => { x = e.clientX y = e.clientY }) </script> uses non-reactive plain variables, so position won't update reactively. <template><div>Mouse at {{ x }}, {{ y }}</div></template> <script setup> const x = ref(0) const y = ref(0) window.addEventListener('mousemove', e => { x.value = e.clientX y.value = e.clientY }) </script> renders UI, so not renderless. <template><slot /></template> <script setup> import { reactive } from 'vue' const position = reactive({ x: 0, y: 0 }) window.addEventListener('mousemove', e => { position.x = e.clientX position.y = e.clientY }) </script> exposes slot without props, so no data passed. <template><slot :pos="position" /></template> <script setup> import { reactive } from 'vue' const position = reactive({ x: 0, y: 0 }) window.addEventListener('mousemove', e => { position.x = e.clientX position.y = e.clientY }) </script> exposes reactive position object via slot prop, clean and correct.

3. Final Answer:

   Expose reactive position object via slot prop without rendering UI -> Option B

4. Quick Check:

   Renderless = slot with reactive data [OK]

Hint: Expose reactive data via slot props, no UI elements [OK]

Common Mistakes:

• Rendering UI inside renderless component
• Not passing data via slot props
• Passing data but not reactive or incomplete