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

jvc-hltb

v1.0.2

Published

A robust HowLongToBeat API client for Node.js that automatically extracts dynamic API keys using multiple methods to ensure reliable access to HLTB data

Readme

jvc-hltb

A robust HowLongToBeat API client for Node.js that automatically captures the dynamic credentials HLTB requires (Puppeteer request interception) to ensure reliable access to HLTB data.

npm version npm downloads License: MIT

Author: JavocSoft

🎮 Features

  • ✅ Automatic credential capture - Uses Puppeteer to intercept the site's own search call and keep the credentials it used
  • ✅ Handles the rotating key - Sends x-auth-token, x-hp-key and x-hp-val, plus the body field whose name is the key of the day
  • ✅ Smart caching - Caches credentials for a configurable time (default 30 minutes) to minimize browser launches
  • ✅ Auto-recovery - Recaptures once and retries when credentials go stale (401/403/404)
  • ✅ Failure cooldown - After a failed capture it stops relaunching the browser for 30 minutes, so a broken HLTB site can't spawn a browser per lookup
  • ✅ Alias matching - Also matches alternative and regional titles via game_alias
  • ✅ Clean API - Simple, promise-based interface
  • ✅ TypeScript support - Includes type definitions

📦 Installation

npm install jvc-hltb

Prerequisites

This library uses Puppeteer, which requires Chromium. On Linux servers, you may need to install additional dependencies:

# Ubuntu/Debian
sudo apt-get install -y \
    ca-certificates \
    fonts-liberation \
    libasound2 \
    libatk-bridge2.0-0 \
    libatk1.0-0 \
    libcups2 \
    libdbus-1-3 \
    libdrm2 \
    libgbm1 \
    libgtk-3-0 \
    libnspr4 \
    libnss3 \
    libx11-xcb1 \
    libxcomposite1 \
    libxdamage1 \
    libxrandr2 \
    xdg-utils

Since npm 11, post-install scripts are blocked by default, so npm install may not download Chrome (it is mentioned in passing among the warnings as allow-scripts ... puppeteer (postinstall)). The install finishes in seconds, looks fine, and then the library fails to launch the browser. Install it explicitly:

npx puppeteer browsers install chrome
npx puppeteer browsers list

🚀 Quick Start

const HLTBClient = require('jvc-hltb');

// Create a new client instance
const hltb = new HLTBClient();

// Search for a game
async function main() {
  // Get game duration
  const duration = await hltb.getGameDuration('The Legend of Zelda: Breath of the Wild');
  
  if (duration) {
    console.log(`Main Story: ${duration.mainStory} hours`);
    console.log(`Main + Extras: ${duration.mainExtras} hours`);
    console.log(`Completionist: ${duration.completionist} hours`);
    console.log(`HLTB URL: https://howlongtobeat.com/game/${duration.gameId}`);
  }
  
  // Clean up when done
  await hltb.destroy();
}

main();

📖 API Reference

new HLTBClient(options?)

Creates a new HowLongToBeat client instance.

Options

| Option | Type | Default | Description | |--------|------|---------|-------------| | cacheMinutes | number | 30 | How long to cache captured credentials (in minutes) | | failureCooldownMinutes | number | 30 | How long to stop relaunching the browser after a failed capture | | enabled | boolean | true | Enable/disable the service | | userAgent | string | Chrome 131 UA | User-Agent used to capture and to replay requests |

const hltb = new HLTBClient({
  cacheMinutes: 60, // Cache credentials for 1 hour
});

⚠️ The auth token embeds the client IP and the User-Agent, so a token captured on one machine will not work on another, and userAgent must be identical for capture and replay.

hltb.getGameDuration(gameName)

Gets the completion times for a game.

Parameters

  • gameName (string) - The name of the game to search for

Returns

Returns a Promise<DurationData | null>:

interface DurationData {
  gameId: number;        // HLTB game ID (for building URLs)
  mainStory: number;     // Main story completion time in hours
  mainExtras: number;    // Main + extras completion time in hours  
  completionist: number; // 100% completion time in hours
}

Returns null if the game is not found or no exact match exists.

Example

const duration = await hltb.getGameDuration('Mega Man');
// {
//   gameId: 5803,
//   mainStory: 2.78,
//   mainExtras: 3.05,
//   completionist: 3.11
// }

hltb.searchGame(gameName)

Searches for games matching the given name. Returns raw results from HLTB API.

Parameters

  • gameName (string) - The search query

Returns

Returns a Promise<Array> with raw game data from HLTB, or null on error.

const results = await hltb.searchGame('Zelda');
// Returns array of game objects with properties like:
// - game_id
// - game_name
// - comp_main (seconds)
// - comp_plus (seconds)
// - comp_100 (seconds)
// - game_image
// - etc.

hltb.formatDuration(hours)

Formats a duration in hours to a human-readable string.

Parameters

  • hours (number) - Duration in hours

Returns

Returns a formatted string like "12h 30m" or null if hours is invalid.

hltb.formatDuration(12.5);  // "12h 30m"
hltb.formatDuration(8);     // "8h"
hltb.formatDuration(0.75);  // "0h 45m"

hltb.destroy()

Cleans up resources (closes any open Puppeteer browser instances).

await hltb.destroy();

🔧 How It Works

HowLongToBeat.com protects its search endpoint with credentials that rotate and that cannot be forged (the token embeds the caller's IP and User-Agent). This library:

  1. Launches a headless browser using Puppeteer
  2. Intercepts the site's own search request and keeps its x-auth-token, x-hp-key and x-hp-val
  3. Caches those credentials for efficient reuse (default: 30 minutes) - the browser opens once per cache window, not per search
  4. Replays plain HTTP against POST /api/search/site, changing only the search terms
  5. Auto-recovers from 401/403/404 by recapturing once and retrying
  6. Backs off for 30 minutes after a failed capture instead of relaunching a browser on every lookup

Architecture

┌─────────────────────────────────────────────────────────────┐
│  Your Application                                           │
│  - hltb.getGameDuration('Game Name')                       │
└────────────────┬────────────────────────────────────────────┘
                 │
┌────────────────▼────────────────────────────────────────────┐
│  jvc-hltb                                                   │
│                                                             │
│  ┌─────────────────────────────────────────────────────┐   │
│  │ Credential Management                               │   │
│  │ - Capture with Puppeteer (headless browser)        │   │
│  │ - Cache credentials for 30 minutes                 │   │
│  │ - Recapture once on 401/403/404                    │   │
│  │ - Cool down 30 min after a failed capture          │   │
│  └─────────────────────────────────────────────────────┘   │
│                                                             │
│  ┌─────────────────────────────────────────────────────┐   │
│  │ Search                                              │   │
│  │ - POST /api/search/site                            │   │
│  │ - Headers: x-auth-token, x-hp-key, x-hp-val        │   │
│  │ - Body also carries a field named after the key    │   │
│  └─────────────────────────────────────────────────────┘   │
└────────────────┬────────────────────────────────────────────┘
                 │
┌────────────────▼────────────────────────────────────────────┐
│  HowLongToBeat API                                          │
│  - Returns game data with completion times                  │
│  - Times in seconds (converted to hours by library)        │
└─────────────────────────────────────────────────────────────┘

🧪 Testing

Run the included test:

npm test

Or test with a specific game:

node test/test.js "Super Mario Bros."

📝 Examples

Basic Usage

const HLTBClient = require('jvc-hltb');

async function main() {
  const hltb = new HLTBClient();
  
  const games = [
    'The Legend of Zelda: Breath of the Wild',
    'Super Mario Odyssey',
    'Hollow Knight'
  ];
  
  for (const game of games) {
    const duration = await hltb.getGameDuration(game);
    if (duration) {
      console.log(`\n${game}:`);
      console.log(`  Story: ${hltb.formatDuration(duration.mainStory)}`);
      console.log(`  Extras: ${hltb.formatDuration(duration.mainExtras)}`);
      console.log(`  100%: ${hltb.formatDuration(duration.completionist)}`);
    } else {
      console.log(`\n${game}: Not found`);
    }
  }
  
  await hltb.destroy();
}

main();

With Custom Options

const HLTBClient = require('jvc-hltb');

const hltb = new HLTBClient({
  cacheMinutes: 60,  // Cache credentials for 1 hour
});

// Your code here...

Error Handling

const HLTBClient = require('jvc-hltb');

async function getGameTime(gameName) {
  const hltb = new HLTBClient();
  
  try {
    const duration = await hltb.getGameDuration(gameName);
    
    if (!duration) {
      console.log('Game not found or no exact match');
      return null;
    }
    
    return {
      name: gameName,
      hours: duration.mainStory,
      url: `https://howlongtobeat.com/game/${duration.gameId}`
    };
    
  } catch (error) {
    console.error('HLTB error:', error.message);
    return null;
  } finally {
    await hltb.destroy();
  }
}

⚠️ Important Notes

  1. Puppeteer requirement: This library uses Puppeteer to capture credentials, which downloads Chromium (~170MB). Consider this for deployment.

  2. Rate limiting: While this library caches credentials, avoid making too many requests in a short time to respect HLTB's servers.

  3. Exact matches only: getGameDuration() returns data only for exact name matches (case-insensitive), including game_alias. Use searchGame() for fuzzy results.

  4. Headless browser: The first request may take a few seconds as Puppeteer launches a browser. Subsequent requests reuse the cached credentials.

  5. Times of 0 mean "no data", not "0 hours" - the library maps them to null.

  6. The token is bound to your IP: behind a rotating proxy or NAT egress a captured token can stop working immediately. The recapture-and-retry covers it, but it explains intermittent 403s.

Troubleshooting

| Symptom | Likely cause | |---------|--------------| | No search request was seen; HLTB may have moved the route again | HLTB changed the search route. See below. | | Navigation timeout of 30000 ms exceeded | Not enough RAM - Chrome never loads the page. 1 GB is not enough; 2 GB works. Fix memory before suspecting the API. | | Could not find Chrome (ver. ...) | Post-install script was skipped. Run npx puppeteer browsers install chrome. | | Everything returns null, nothing throws | Usually the route move above; check the log for the capture warning. |

If HLTB moves the search route again, it can be found without a browser:

UA='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'
curl -s -A "$UA" https://howlongtobeat.com/ -o page.html
grep -oE '/_next/static/chunks/[a-zA-Z0-9._/-]+\.js' page.html | sort -u > chunks.txt
mkdir -p js && cd js
while read -r u; do curl -s -A "$UA" "https://howlongtobeat.com$u" -O; done < ../chunks.txt
grep -ohE '"/api/[a-zA-Z0-9_/-]*"' *.js | sort -u

The right one is the route used inside a fetch(..., { method: "POST" }) carrying the x-auth-token, x-hp-key and x-hp-val headers. Update SEARCH_PATH in src/index.js (or pass a different searchPath on the instance).

🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

📄 License

MIT © JavocSoft

This project is licensed under the MIT License - you are free to use, modify, distribute, and create your own versions of this library for any purpose, including commercial use.

🙏 Acknowledgments

  • HowLongToBeat.com for providing game completion time data
  • The gaming community for making this data available

Note: This library is not affiliated with HowLongToBeat.com. Please use responsibly and respect their terms of service.