opensourceprojects.dev

A broadsheet for software that doesn't ask for your email

Product tours, highlights and hints for the web, no dependencies
GitHub RepoViews15

Project Description

View on GitHub

Driver.js: Product Tours and Onboarding Without the Dependency Bloat

You've built something worth showing off, but users land in your app and immediately get lost. The search bar is right there—they can't find it. The "New project" button is staring at them—they click everything else first. You could write your own tooltip system, but that means handling focus management, keyboard navigation, and screen reader announcements, which is a lot of work you didn't sign up for. Driver.js is a library that handles product tours, highlights, hints, and onboarding checklists for the web, and it does all of it with no dependencies.

What It Does

Driver.js is a TypeScript library for guiding users through your interface. It covers four main use cases: tours that walk users through your app step by step, highlights that dim the page around any element (with or without a popover), hints that appear as pulsing beacons you click to open a popover, and checklists that serve as an onboarding widget whose items start tours and tick themselves off.

The library works with any framework and ships as separate entry points for different features—driver.js/hints, driver.js/checklist, and driver.js/headless—so you only pull in what you need. It's themeable through plain CSS classes and variables, and it's built with accessibility in mind: keyboard control, focus management, and screen reader announcements are part of the package. It's MIT licensed, so it's free for personal and commercial use.

Why It's Cool

No dependencies, written in TypeScript. This is the kind of thing that matters more than it sounds. A lot of onboarding libraries drag in a framework or a UI toolkit as a peer dependency, which means you're now maintaining two things. Driver.js doesn't care what you're building with—React, Vue, Svelte, or plain HTML—it just works.

Action-driven steps are the standout feature. Most tour libraries assume the user will click "Next" and move on. Driver.js lets a step wait for the user to actually do something—click, type, or pick—and give feedback on wrong actions. You can define a step with advanceOn: "click" so the tour only progresses when the user clicks the right element. That's a meaningful shift from "read this tooltip" to "learn by doing."

waitForElement handles real-world timing. If a step depends on an element that doesn't exist yet (maybe it appears after an API call or a modal opens), you can set waitForElement: 3000 and the tour will wait up to three seconds for it. It's a small detail that solves a genuinely annoying problem.

Accessibility isn't an afterthought. Keyboard control, focus management, and screen reader announcements are built in. If you've ever tried to retrofit accessibility into a custom tooltip system, you know how much work that is. Here it's just part of the library.

The API is refreshingly simple. You configure an object with steps, call drive(), and you're done. Highlighting a single element is a one-liner. There's no ceremony, no provider wrapping, no context setup—just import and go.

How to Try It

Getting started takes about two minutes. Install it from npm:

npm install driver.js

Then import the library and its stylesheet, configure your steps, and call drive():

import { driver } from "driver.js";
import "driver.js/dist/driver.css";

const driverObj = driver({
  showProgress: true,
  steps: [
    { element: "#search", popover: { title: "Search", description: "Find anything from here." } },
    { element: "#new-project", popover: { title: "New project", description: "Start your first project." } },
  ],
});

driverObj.drive();

If you just want to highlight a single element without a full tour, use driverObj.highlight() with the same element and popover config. For interactive steps, add advanceOn: "click" and an instruction field to tell the user what to do.

The documentation site has guides, live demos, and the full reference. The repo is at github.com/nilbuild/driver.js, and it's a pnpm monorepo—the library lives in packages/driver, with a playground in apps/playground and docs in apps/docs. Both apps import the library from source, so if you want to contribute, changes show up immediately. Run pnpm install then pnpm dev for the playground, or pnpm test for unit tests.

Final Thoughts

Driver.js is a focused tool that does a specific job well. It's not trying to be a full onboarding platform—there's no analytics dashboard, no user segmentation, no A/B testing. What you get is a clean, dependency-free library for tours, highlights, hints, and checklists, with accessibility and interactivity baked in. If you're building a web app and you need to show users around (or just point at one thing), this is worth a look. It's the kind of library that saves you a weekend of work and a headache you didn't need.


Follow @githubprojects for more developer tools and open source projects.

Back to Projects
Project ID: driver-jsLast updated: November 16, 2026 at 08:59 AM