npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

react-product-tour-guide

v0.2.2

Published

A flexible and accessible product tour component for React applications

Readme

React Product Tour

A flexible and accessible product tour component for React applications.

Features

  • Spotlight focus on target elements with smooth highlighting
  • Multiple content types: text, images, videos, custom React components
  • Fully accessible — ARIA attributes, keyboard navigation, screen reader support
  • Dark mode support via CSS variables and .dark class
  • Three animation styles: slide, bounce, fade
  • Progress indicator
  • Async step support via waitFor
  • Customizable styling via CSS variables, class names, or fully custom button renders
  • Error boundaries for graceful media failure degradation
  • Debounced scroll/resize handling for smooth repositioning

Installation

npm install react-product-tour-guide

Styles are loaded automatically — no separate CSS import needed.

Quick Start

import { TourProvider, Tour, useTour } from "react-product-tour-guide";

const steps = [
  {
    selector: "#welcome",
    content: "Welcome to our app!",
    placement: "bottom",
  },
  {
    selector: "#features",
    content: "Check out our amazing features!",
    placement: "right",
  },
];

function TourButton() {
  const { start } = useTour();
  return <button onClick={start}>Start Tour</button>;
}

function App() {
  return (
    <TourProvider steps={steps} onComplete={() => console.log("Tour done!")}>
      <TourButton />
      <Tour />
      {/* rest of your app */}
    </TourProvider>
  );
}

Tour renders the overlay and tooltip into a portal. TourProvider manages state. useTour exposes controls anywhere in the tree.

API Reference

TourProvider Props

| Prop | Type | Default | Description | | --------------- | ----------------------- | -------- | -------------------------------------- | | steps | TourStep[] | required | Array of tour steps | | children | ReactNode | required | Child components | | defaultActive | boolean | false | Start tour automatically on mount | | onComplete | () => void | — | Called when the last step is completed | | onSkip | () => void | — | Called when the tour is skipped | | onStepChange | (index, step) => void | — | Called after navigating to a new step | | onStepEnter | (index, step) => void | — | Called when entering a step | | onStepExit | (index, step) => void | — | Called when leaving a step |

Tour Props

| Prop | Type | Default | Description | | -------------------------- | ------------------------------- | --------- | ----------------------------------------------------- | | skip | boolean | true | Show the Skip button | | showProgress | boolean | false | Show a progress bar and "Step X of Y" counter | | animation | 'slide' \| 'bounce' \| 'fade' | 'slide' | Tooltip entrance animation | | overlayClassName | string | — | Class applied to the overlay | | tooltipClassName | string | — | Class applied to the tooltip | | buttonClassName | string | — | Class applied to all buttons | | buttonContainerClassName | string | — | Class applied to the button container | | highlightTarget | boolean \| HighlightConfig | true | Highlight the target element | | tooltipOffset | number | 10 | Distance in pixels between the tooltip and its target | | dismissOnOverlayClick | boolean | true | Close the tour when the dark overlay is clicked | | accessibility | AccessibilityConfig | — | Screen reader and focus options | | buttonConfig | ButtonConfigObj | — | Custom button content or render functions |

useTour

Returns the tour context:

const {
  steps, // TourStep[]
  currentStep, // number
  isActive, // boolean
  start, // () => void
  stop, // () => void
  next, // () => Promise<void>  — awaits step.waitFor if present
  back, // () => void
  skip, // () => void
} = useTour();

useTour must be used inside a TourProvider.

TourStep

| Property | Type | Description | | ----------- | ---------------------------------------- | ------------------------------------------------ | | selector | string | CSS selector for the target element | | title | string | Optional heading shown at the top of the tooltip | | content | ReactNode \| ContentType | Content to display in the tooltip | | placement | 'top' \| 'bottom' \| 'left' \| 'right' | Tooltip placement | | waitFor | () => Promise<void> | Async gate before advancing to this step |

ContentType

| Property | Type | Description | | -------- | ------------------------------------------ | ------------------------------------------------------ | | type | 'text' \| 'image' \| 'video' \| 'custom' | Content type | | value | ReactNode \| string \| MediaSource | Content value | | alt | string | Alt text for image content (default: 'Tour content') | | props | Record<string, unknown> | Extra props forwarded to the element |

MediaSource

| Property | Type | Description | | -------- | --------------------- | ----------------- | | type | 'remote' \| 'local' | Media source type | | src | string | URL or asset path |

AccessibilityConfig

| Property | Type | Description | | -------------------- | ---------------------- | ----------------------------------- | | enableScreenReader | boolean | Enable aria-live announcements | | announcements | { start, end, step } | Custom announcement strings | | focusManagement | 'auto' \| 'manual' | Focus strategy | | focusTrap | boolean | Trap Tab key within the tour dialog |


Content Types

Plain text or ReactNode

Any React-renderable value works — strings, JSX elements, or full components:

{ selector: '#el', content: 'Simple text' }
{ selector: '#el', content: <strong>Bold step</strong> }
{ selector: '#el', content: <FeatureCallout title="New" description="Try it out" /> }

For explicit typing, use type: 'custom':

{ selector: '#el', content: { type: 'custom', value: <FeatureCallout /> } }

Image

{
  selector: '#el',
  content: {
    type: 'image',
    value: 'https://example.com/screenshot.jpg',
    alt: 'Feature screenshot',
    props: { className: 'rounded-lg' },
  },
}

Video

{
  selector: '#el',
  content: {
    type: 'video',
    value: { type: 'remote', src: 'https://example.com/demo.mp4' },
    props: { poster: 'https://example.com/thumb.jpg' },
  },
}

Custom component

{
  selector: '#el',
  content: {
    type: 'custom',
    value: (
      <div>
        <h3>Custom content</h3>
        <p>Any React elements work here.</p>
      </div>
    ),
  },
}

Async step (waitFor)

{
  selector: '#async-panel',
  content: 'Panel loaded!',
  waitFor: () => new Promise(resolve => {
    // Resolve when the element is ready
    const el = document.querySelector('#async-panel');
    if (el) resolve();
    else setTimeout(resolve, 500);
  }),
}

Theming

CSS Variables

Override variables in your app's CSS to theme the tour globally:

:root {
  --tour--overlay--background: rgba(0, 0, 0, 0.6);

  --tour--tooltip--background: white;
  --tour--tooltip--text: black;
  --tour--tooltip--border: #e5e7eb;
  --tour--tooltip--border-width: 1px;
  --tour--tooltip--radius: 0.5rem;
  --tour--tooltip--padding: 1rem;
  --tour--tooltip--gap: 0.5rem;
  --tour--tooltip--shadow: 0 4px 6px -1px rgba(0, 0, 0, 0.1);
  --tour--tooltip--transition: all 0.2s ease-in-out;
  --tour--tooltip--max-width: 300px;

  --tour--button--primary--background: #646cff;
  --tour--button--primary--text: white;
  --tour--button--secondary--background: #e5e7eb;
  --tour--button--secondary--text: #374151;

  --tour--highlight--padding: 8px;
  --tour--highlight--radius: 10px;

  --tour--progress--background: #e5e7eb;
  --tour--progress--fill: #f43f5e;
}

Dark Mode

Add the .dark class to any ancestor element (typically <html>):

.dark {
  --tour--tooltip--background: #1f2937;
  --tour--tooltip--border: #374151;
  --tour--tooltip--text: #f9fafb;
}

Custom Classes

Pass any CSS class names via the className props. When using Tailwind, prefix utilities with ! to ensure they override the library's base styles:

<Tour
  overlayClassName="!bg-indigo-900/70"
  tooltipClassName="!bg-slate-900 !text-white !border-slate-700 !rounded-2xl"
  buttonClassName="!rounded-full"
/>

Without Tailwind, plain CSS classes work when your rules are unlayered (unlayered styles always win over the library's @layer react-product-tour styles):

.my-tooltip {
  background: #1e293b;
  color: #f1f5f9;
  border-radius: 1rem;
}
<Tour tooltipClassName="my-tooltip" />

Custom Button Rendering

<Tour
  buttonConfig={{
    primary: {
      content: "Continue →",
      className: "bg-indigo-500 text-white px-6 py-2 rounded-lg",
    },
    secondary: {
      content: "← Back",
    },
    // Or full custom render:
    primary: {
      render: ({ onNext, onComplete, isLastStep, currentStep, totalSteps }) => (
        <button onClick={isLastStep ? onComplete : onNext}>
          {isLastStep ? "Finish" : `Next (${currentStep + 1}/${totalSteps})`}
        </button>
      ),
    },
    // Custom container layout:
    container: {
      render: (props) => (
        <div className="flex flex-col gap-3 mt-4 pt-4 border-t">
          <button onClick={props.isLastStep ? props.onComplete : props.onNext}>
            {props.isLastStep ? "Done" : "Next"}
          </button>
          {!props.isFirstStep && <button onClick={props.onBack}>Back</button>}
        </div>
      ),
    },
  }}
/>

Callbacks

<TourProvider
  steps={steps}
  onStepChange={(index, step) => analytics.track("tour_step", { index })}
  onStepEnter={(index, step) => console.log("entered", step.selector)}
  onStepExit={(index, step) => console.log("exited", step.selector)}
  onComplete={() => localStorage.setItem("tour_done", "1")}
  onSkip={() => console.log("skipped")}
>
  <Tour />
</TourProvider>

Keyboard Navigation

The tour responds to keyboard events out of the box — no configuration required:

| Key | Action | | ------------------- | -------------------------------------------------------------- | | Escape | Close / skip the tour | | / | Advance to the next step | | / | Go back to the previous step | | Tab / Shift+Tab | Move focus between buttons (focus trap when focusTrap: true) |

Arrow keys are ignored when focus is inside an input, textarea, or select.


Accessibility

Focus management and the Tab focus trap are active by default — they do not require enableScreenReader. Set enableScreenReader: true only to add aria-live screen reader announcements:

<Tour
  accessibility={{
    enableScreenReader: true,
    announcements: {
      start: "Product tour started. Press Tab to navigate.",
      end: "Tour complete.",
      step: "Step {step} of {total}: {content}",
    },
    focusTrap: true, // default — trap Tab within the dialog
    focusManagement: "auto", // default — auto-focus first button; restore on close
  }}
/>

Global Manager (without context)

For use cases where TourProvider can't wrap your component tree:

import { tourManager } from "react-product-tour-guide";

tourManager.initialize(steps);
tourManager.start();
tourManager.next();
tourManager.stop();

// Subscribe to state changes
const unsubscribe = tourManager.subscribe((state) => {
  console.log(state.isActive, state.currentStep);
});
unsubscribe(); // cleanup

Exported Types

All public types are exported for TypeScript consumers:

import type {
  TourStep, // A single step definition
  TourProviderProps, // Props for <TourProvider>
  TourProps, // Props for <Tour>
  Placement, // 'top' | 'bottom' | 'left' | 'right'
  ContentType, // Structured content (image/video/custom)
  MediaSource, // { type: 'remote'|'local', src: string }
  HighlightConfig, // { className?, style? } for the spotlight ring
  AccessibilityConfig, // Screen reader and focus trap options
  ButtonConfig, // Per-button content/className/style/render
  ButtonLayoutConfig, // Button container direction/align/gap/render
  ButtonRenderProps, // Props passed to custom button render functions
} from "react-product-tour-guide";

Testing

The library ships with 95 unit + snapshot tests. Run them with:

npm test

To update DOM snapshots after intentional UI changes:

npm test -- -u

Contributing

See CONTRIBUTING.md for setup instructions, coding standards, and PR guidelines.

License

MIT — see LICENSE for details.

Support

Buy me a coffee: buymeacoffee.com/guestdm