Custom Tooltip Directive in Vuejs 3: Tutorial

Valerio Barbera
How to implement a reusable tooltip directive in Vuejs 3

Custom directives in Vuejs 3 are one of those things where there is no compatibility with the previous version of the framework. 

Working on the new version of the Inspector frontend dashboard I had the need to show tooltips in many different points of the application. The goal was immediately to avoid duplicate code.

Before entering the implementation of a custom tooltip directive in Vuejs 3 let me introduce the fundamentals of a good code reuse strategy in Vuejs.

Code reuse in Vuejs

The most important forms for code reuse in Vuejs are components and composable if you write components with composition API.

The benefit of using components is that you can create complex user interfaces with ease, by breaking them down into smaller, reusable pieces. This makes it easier to maintain your code and allows you to make improvements to the user interface incrementally.

Vuejs provides other options for code reuse, such as mixins, directives, and plugins, which can further improve your code’s maintainability and reusability. Mixins are reusable code blocks that can be added to a component (no more recommended in Vuejs 3), while directives are used to add custom behavior to HTML elements. Plugins, on the other hand, are packages that can be installed and used across multiple components in your application.

By leveraging these features, you can create powerful, scalable applications that are easy to maintain and extend.

If you want learn more strategies used to build our platform check out this article on how to implement an event-bus in Vuejs 3:

Custom directives in Vuejs 3

As mentioned in the documentation:

Custom directives, on the other hand, are mainly intended for reusing logic that involves low-level DOM access on plain elements.

A perfect tool to add features like “tooltip”, “popover” and other Bootstrap components to DOM elements.

A directive in Vuejs is essentially an object with the same properties and hooks used in components. But in this case the hooks will receive the instance of the DOM element the directive is bound to.

export default {
    mounted(el) {

To register the directive and make it available in the template you must pass the directive object to the app instance:

const app = createApp({})
import tooltip from "./Directives/tooltip";
// make v-tooltip usable in all components
app.directive('tooltip', tooltip);

You can check out all the available lifecycle hooks in the official documentation.

Custom tooltip directive for Vuejs 3

Why do we need to create a directive to show tooltips?

As mentioned in the Bootstrap 5 documentation you have to initialize Tooltips with javascript to make it visible:

// HTML in your view
<a href="#" data-bs-toggle="tooltip" data-bs-title="Hello World!">Tooltip Example</a>

// Enable tooltip via Javascript 
const tooltipTriggerList = document.querySelectorAll('[data-bs-toggle="tooltip"]');
const tooltipList = [...tooltipTriggerList].map(tooltipTriggerEl => new bootstrap.Tooltip(tooltipTriggerEl));

But this code works in a static HTML page, where DOM elements are available yet the time the javascript code runs to activate all the tooltips in the view.

But a reactive frontend application works in the opposite way. Components are loaded dynamically with the user interaction. So every tooltip included in the view after the first application bootstrap will not be activated and will remain hidden.

We need to attach tooltips to the DOM elements dynamically the time the element is attached to the view.

A perfect use case for a custom directive in Vuejs.

import {Tooltip} from "bootstrap";
// Use "mounted" hook
export default {
    mounted(el, binding) {
        let tooltip = new Tooltip(el, {
            placement: binding.arg || 'top',
            title: binding.value

Register the directive in the app instance to make it available in your components:

import tooltips from "./Directives/tooltips.js";

How to use the tooltip directive

The code above allows you to set the behavior of the tooltip dynamically.

Default usage:

<a href="#" v-tooltip="Hello World!">Tooltip Example</a>
vuejs bootstrap tooltip on top
Tooltip on the top

If you want change the placement of the tooltip you can pass it as an argument:

<a href="#" v-tooltip:right="Hello World!">Tooltip Example</a>
vuejs bootstrap tooltip on the right
Tooltip on the right

New to Inspector? Try it for free now

I hope this article can help you design your software products in a more convenient way. This implementation can be replicated for popover and other Bootstrap components.

Are you responsible for application development in your company? Consider trying my product Inspector to find out bugs and bottlenecks in your code automatically. Before your customers stumble onto the problem.

Inspector is usable by any IT leader who doesn’t need anything complicated. If you want effective automation, deep insights, and the ability to forward alerts and notifications into your messaging environment try Inspector for free. Register your account.

Or learn more on the website:

Related Posts

aws sqs in a large scale laravel application inspector

AWS SQS in a large scale application

In today’s article, I’m going to show you how we use AWS SQS in our Laravel application, and how it helps us to manage 1.6 billion operations each month. In the image below you can see our typical bill for a month of AWS SQS usage: Before entering in the details of our system design

Why and how to create an Event Bus in Vuejs 3

Have you ever used an event bus in Vue 2 and don’t know how to recreate it in Vue 3? Since I’m working on the 2.0 version of my product’s UI (to be released in May) I’m publishing some technical tricks I learn migrating my application from Vuejs 2 to Vuejs 3. The current version

How to make Vite Hot Module Replacement work on Windows

As many of our community members already know, we recently started the renovation of the Inspector dashboard UI with a fresh new design and a modern technology stack. In this article I will explain why we decided to leave Webpack and embrace Vite as assets build tool and Hot Module Replacement. I will show you