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

@techwarq/tour-engine

v0.1.0

Published

Instrument your app to capture flows for launchvid — screenshots, screen recording, waypoints, interactions.

Readme

@techwarq/tour-engine

Instrument your app to capture real product flows — screenshots, screen recordings, interaction data, and waypoints — then feed them to launchvid to generate polished launch videos.


Install

npm install @techwarq/tour-engine

Quick start

1. Create tour.config.ts in your project root

import type { TourConfig } from '@techwarq/tour-engine';

const config: TourConfig = {
  project_name: "MyProduct",
  output_dir: "./tour-output",
  app_url: "http://localhost:3000",   // your dev server
  capture: {
    screenshots: true,
    video: true,
    interactions: true,
    components: true,
  },
};

export default config;

2. Wrap your app root

Next.js App Router (app/layout.tsx):

import { TourProvider } from '@techwarq/tour-engine';
import tourConfig from '../tour.config';

export default function RootLayout({ children }) {
  return (
    <html>
      <body>
        <TourProvider config={tourConfig}>{children}</TourProvider>
      </body>
    </html>
  );
}

React / Vite (src/main.tsx):

import { TourProvider } from '@techwarq/tour-engine';
import tourConfig from '../tour.config';

ReactDOM.createRoot(document.getElementById('root')!).render(
  <TourProvider config={tourConfig}>
    <App />
  </TourProvider>
);

Vue 3 (src/main.ts):

import { TourPlugin } from '@techwarq/tour-engine';
import tourConfig from '../tour.config';

app.use(TourPlugin, tourConfig);

3. Mark key pages with waypoints

import { TourWaypoint } from '@techwarq/tour-engine';

export default function Dashboard() {
  return (
    <TourWaypoint name="dashboard" description="Main application dashboard">
      <div className="dashboard">...</div>
    </TourWaypoint>
  );
}

Or use the hook:

import { useTourWaypoint } from '@techwarq/tour-engine';

const ref = useTourWaypoint({ name: "dashboard", description: "Main dashboard" });
return <div ref={ref}>...</div>;

4. Add the capture script to package.json

{
  "scripts": {
    "tour:capture": "tour-engine capture --config tour.config.ts"
  }
}

5. Start your app, then capture

# Terminal 1
npm run dev

# Terminal 2
npm run tour:capture

Captured assets are written to ./tour-output/<project_name>/:

tour-output/MyProduct/
├── manifest.json          ← launchvid reads this
├── screenshot-hero.png
├── screenshot-dashboard.png
├── screenshot-pricing.png
└── session.webm           ← full session recording

6. Generate your launch video

launchvid --sdk

CLI reference

tour-engine capture [options]

Options:
  -c, --config <path>   Path to tour.config.ts (default: "tour.config.ts")
  -u, --url <url>       App URL, overrides config.app_url
  -v, --verbose         Print each waypoint as it is captured
  -h, --help

TourConfig reference

| Field | Type | Required | Description | |-------|------|----------|-------------| | project_name | string | ✓ | Used as output folder name and in the manifest | | output_dir | string | ✓ | Where to write captured assets | | app_url | string | | Dev server URL (default: http://localhost:3000) | | capture.screenshots | boolean | | Capture screenshots at each waypoint | | capture.video | boolean | | Record a full session video | | capture.interactions | boolean | | Log click and focus events | | capture.components | boolean | | Collect data-component attribute values |


How it works

  1. TourProvider / TourPlugin instruments your React/Vue app at runtime and sets data-tour-waypoint attributes on marked elements.
  2. tour-engine capture launches a headless Playwright browser, navigates to your running app, and finds all [data-tour-waypoint] elements.
  3. At each waypoint it scrolls into view, waits for animations to settle, and takes a 1920×1080 screenshot.
  4. A full session video is recorded by Playwright's built-in recorder.
  5. Click and focus events are intercepted via an injected script.
  6. Everything is written to manifest.json in the output directory, which launchvid --sdk reads.