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

qi-graphql

v0.1.1

Published

Query GraphQL

Downloads

11

Readme

QI - test your GraphQL

I felt pain with all the graphiql clones. Authorization and re-authorization is nightmare and I missed some other features, too (view headers, timings, possibility to save something from the result of one query and use it in subsequent or another query - like pagination token, etc.).

Currently only barebone cli available and highly opinionated - it serves my needs but I'm willing to make it much better, because I'm working on more projects.

And as you can see... very bare documentation and probably very buggy. Not ready for prime time but if you feel the same pain, I'm happy to cooperate and make it better.

How to use it

npm install -D qi-graphql

Create folder for config

mkdir .qi

Create settings.json there (example):

{
  "queries": ["queries/*.gql"],
  "vars": ["queries/*.vars.js"],
  "servers": {
    "myserver": {
      "url": "https://some/graphql"
    }
  },
  "clients": {
    "authLambda": {
      "server": "myserver",
      "default": true,
      "authorizer": {
        "source": "qi-cognito",
        "credentials": {
          "username": "xxxx",
          "password": "xxxx",
          "userPoolId": "xxxx",
          "clientId": "xxxx"
        }
      }
    },
  }
}

Create some queries in the folder queries (or any other but reflect "queries" section in settings). You can see some examples in the examples/queries folder in the repo.

Run the query

qi query -q yourquery

See qi help or qi query help.

More documentation to come.