npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2024 – Pkg Stats / Ryan Hefner




eslint rules for got





(for the sake of a better name)


yarn add -D eslint-plugin-got

# or

npm install -D eslint-plugin-got

Add to .eslintrc.js or equivalents in plugins/rules section:

module.exports = {
  plugins: ['got'],
  rules: {
    'got/no-leading-slash': ['error', { imports: ['^got$', '^ky$'] }],

Disallow leading slashes in requests


If you are using got or ky with the prefixUrl option and constantly forget that you mustn't use a leading slash, this rule is for you.

This works for all request libraries with the same API and input restrictions. So you can use it for got, ky or any created instances of it. You just need to specify the imports option in the configuration.

This is auto fixable.

// Api.ts
import got from 'got'
export default got.extend({ prefixUrl: '' })
// .eslintrc.js
module.exports = {
  // all imports matching the pattern ".+/Api$" will be considered for linting
  'got/no-leading-slash': ['error', { imports: ['.+/Api$'] }],


import api from './Api'


import api from './Api'
// The request input should not start with a leading slash. (at 2:8)
// -----^

// -----^

The import call itself and the request method shortcuts will be checked:

api('request', ...args)
api.get('request', ...args)'request', ...args)
api.put('request', ...args)
api.patch('request', ...args)
api.head('request', ...args)
api.delete('request', ...args)



Type: array
Default: []

To enable the lint rule you can add regex pattern(s) which should match the import source (file or package):

  "got/no-leading-slash": ["error", { "imports": [".+/Api$"] }]

If you also want to prevent leading slashes in the calls of the packages got, ky and ky-universal you could use following config:

  "got/no-leading-slash": [
    { "imports": ["^got$", "^ky$", "^ky-universal$", ".+/Api$"] }


This rule enforces that every request going through got, ky or an instance of it with the prefixUrl enabled must not start with a leading slash:

Note: Leading slashes in input are disallowed when using this option to enforce consistency and avoid confusion. For example, when the prefix URL is and the input is /bar, there's ambiguity whether the resulting URL would become or The latter is used by browsers.