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

tourneyradar

v0.1.0

Published

Typed client for the TourneyRadar API: over-the-board chess tournaments in 70+ countries.

Downloads

159

Readme

tourneyradar

Typed TypeScript client for the TourneyRadar API: over-the-board chess tournaments across 70+ countries.

npm install tourneyradar

Use it

No key needed. The API is keyless.

import { TourneyRadar } from 'tourneyradar';

const chess = new TourneyRadar();

const { data, meta } = await chess.list({ country: 'IN', upcoming: true });
console.log(`${meta.total} tournaments, showing ${data.length}`);

With a key

A key raises your rate limit from 100 to 600 requests a minute. Every endpoint works without one.

const chess = new TourneyRadar({ apiKey: process.env.TOURNEYRADAR_KEY });
const { usage, limit } = await chess.usage();
console.log(`${usage.today} requests today, ceiling ${limit.per_minute}/min`);

Methods

| Method | Returns | |---|---| | list(options?) | A page of tournaments, with meta for pagination | | get(id) | One tournament | | search(query, options?) | A page of search results | | countries() | Every country with tournaments, and how many | | stats() | Dataset-wide counts | | usage() | Your key's usage and ceiling. Needs a key. | | paginate(options?) | An async iterator over every match |

list and paginate take country, category, upcoming, fide_rated, date_from, date_to, organizer, limit and page.

Paginating

paginate fetches pages as you consume them, so breaking out of the loop stops the requests. The dataset is 14,000+ rows; this exists so you do not pull all of it to look at the first ten.

for await (const tournament of chess.paginate({ country: 'DE' })) {
  if (tournament.fide_rated) console.log(tournament.name);
}

Errors

Any non-2xx throws a TourneyRadarError carrying the status, so you can branch without parsing the message.

import { TourneyRadarError } from 'tourneyradar';

try {
  await chess.get('nope');
} catch (err) {
  if (err instanceof TourneyRadarError) {
    if (err.status === 404) console.log('No such tournament');
    if (err.isRateLimited) console.log(`Retry in ${err.retryAfterSeconds}s`);
  }
}

Options

| Option | Default | Notes | |---|---|---| | apiKey | none | Raises your rate limit. Optional. | | baseUrl | the hosted API | Point at a self-hosted instance. | | fetch | global fetch | Supply your own on Node below 18. |

Apache-2.0.