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

next-pr

v1.0.0

Published

Predict the next pull request number for a GitHub repository

Readme

next-pr

Predict the next pull request number for a GitHub repository.

Useful when you need a PR's number before it exists; for example, to reference it in a changelog entry that ships with the PR itself.

CLI

$ npx next-pr nodejs/node
58124

Full GitHub URLs and .git suffixes work too:

$ npx next-pr https://github.com/nodejs/node.git
58124

Unauthenticated requests are limited to 60 per hour by GitHub. Set a GITHUB_TOKEN environment variable to raise the limit (any token with public repo read access works, including the automatic token in GitHub Actions):

$ GITHUB_TOKEN=ghp_... npx next-pr nodejs/node

API

$ npm install next-pr
import { nextPrNumber } from "next-pr";

const number = await nextPrNumber("nodejs/node");
// or: await nextPrNumber("https://github.com/nodejs/node")

console.log(number); // e.g. 58124

nextPrNumber(repo, options?)

  • repo: a owner/repo slug or a github.com URL.
  • options.token: GitHub API token. Defaults to process.env.GITHUB_TOKEN.

Returns a Promise<number>. Rejects with an Error if the repo slug is malformed or the GitHub API returns a non-2xx response (e.g. an unknown repo or a hit rate limit).

parseRepo(input)

The slug/URL parser used internally, exported for convenience. Returns { owner, repo } or throws on invalid input.

Caveats

The result is a prediction, not a reservation: if someone opens an issue or PR between the lookup and your PR, the number will be off by however many landed in between.

License

MIT