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

type-query-language

v0.0.1

Published

better way to add typings for graphql queries

Readme

typeql

Easier way to provide typings for your graphql queries.

Why use typeql

Below is a sample graphql shema but you don't know what kind of data it returns is it an object, an array of objects, etc.

query HeroNameAndFriends(
  $hero_id: String!
  $some_other_id: Int
  $another_string: String!
) {
  hero_by_id(id: $hero_id, some_id: $some_other_id, another: $another_string) {
    name
    friends {
      name
    }
  }
}

After using typeQL. You get a schema which is more descriptive about the data that you are going to get from this query.

query HeroNameAndFriends(
 $hero_id: String!,
 $some_other_id: Int,
 $another_string: String!
) {
  hero_by_id(id: $hero_id, some_id: $some_other_id, another: $another_string): {
    name: String!
    friends: [{
      name: String!
    }]
  }
}

The above will return the graphql query and typings as such

export interface IResult {
  hero_by_id: {
    name: string;
    friends: {
      name: string | null;
    }[];
  };
}
export interface IVariables {
  hero_id: string;
  some_other_id: number | null;
  another_string: string;
}
query HeroNameAndFriends(
  $hero_id: String!
  $some_other_id: Int
  $another_string: String!
) {
  hero_by_id(id: $hero_id, some_id: $some_other_id, another: $another_string) {
    name
    friends {
      name
    }
  }
}

How to use

  • Convert your graphql queries to typeql. Its really simple just take a look inside the tql folder. Note: Remember to seperate your query into multi line or you get wrong output
  • Put files inside tql folder with .tql extension
  • npm run start
  • Get .graphql files in root folder

Known Problems

  • Delete typings folder to remove typings/query...ts not under rootDir.
  • You have to use multiline queries to get the correct typings/graphql-query from your typeql file.