tldr: If your component does not need to be stateful, turning it into a functional components can increase your its rendering performance by 70%.
What is a functional component?
Functional components (not to be confused with Vue’s render functions) is a component which holds no state and no instance.
In more plain English, this means that the component does not support reactivity and cannot make a reference to itself through
Accessing component properties
Without the state or instance, you might wonder how you can reference things like data or methods. Fortunately, Vue provides a “context” parameter to the underlying render function.
This “context” argument is an object with the following properties:
- props: An object of the provided props
- children: An array of the VNode children
- slots: A function returning a slots object
- scopedSlots: (v2.6.0+) An object that exposes passed-in scoped slots. Also exposes normal slots as functions.
- data: The entire data object, passed to the component as the 2nd argument of createElement
- parent: A reference to the parent component
- listeners: (v2.3.0+) An object containing parent-registered event listeners. This is an alias to data.on
- injections: (v2.3.0+) if using the inject option, this will contain resolved injections.
Accessing this “context” parameter is pretty straightforward. For example, if we wanted to do something with props, it might look like this:
A quick note on functional components and props:
In a functional
Why are functional components cool?
Functional components can make accessing your components a little more difficult to work with or introduce some complexity, so why go through the hassle?
Because functional components do not have a state, they do not require extra initialization for things like Vue’s reactivity system.
Functional components will still react to changes like new props being passed in, but within the component itself, there is no way for it to know when it’s data has changed because it does not maintain its own state.
For those of you that prefer hard numbers, I did a benchmark for rendering 1,000 list items as stateful components vs. functional components, and the while the stateful components took on average 140ms, the functional components took about 40ms.
See for yourself: https://codesandbox.io/s/vue-stateful-vs-functional-yterr
For very small applications, you may not notice much of a difference, but for a large application, you should see significant improvements to the DOM render/update events after implementing functional components.
When would you use functional components?
There are, however, some excellent use cases to sprinkle in functional components:
- A component which is simply presentational, AKA a “dumb” component. For example, buttons, pills, tags, cards, even full pages with just static text like an About page.
- A “higher order component” which is used to wrap markup or basic functionality around another component.
- Any time you find yourself in a loop (v-for), the items in the loop are usually great candidates.
ne small issue I’ve run into for a pretty specific use case. When using a
<template> tag, and accepting data through a prop, sometimes we want to modify the data inside the template.
With a standard Vue component, this is easy using either methods or computed props. With functional components, we do not have access to methods or computed props.
However, there is still a way to do this.
Let’s say our component accepts a
"user" prop which is an object
"lastName", and we want to render a template that shows the user’s full name.
In a functional
<template> component, the way we could do this is by providing a method right on our component definition, then use the
$options property provided by Vue to access our special method:
I have not personally run into this other issue, but a community member found that try to nest functional components that have scoped slots, the behavior is not the same as nesting stateful components with scoped slots https://github.com/vuejs/vue-loader/issues/1136.
Another issue I ran into is that functional components cannot have nested component (neither globally or locally registered). This is kind of a big deal, but there is a hacky workaround. The issue was reported in GitHub and the core Vue team admitted it would be a good feature to add, but it’s not likely to be implemented since Vue 3.0 should be out soon, making functional components unnecessary.
If you care about performance or are working on very large applications, consider getting in the practice of creating functional components. The small learning curve is worth the performance gains.