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 🙏

© 2024 – Pkg Stats / Ryan Hefner

gql-pathify

v1.0.8

Published

Parses GraphQL code to a flat list with paths to nodes being used.

Downloads

145,603

Readme

gql-pathify

A lightweight + simple package for translating graphql requests into an array of paths to the nodes.

It won't add fields multiple times that gql will merge when resolving.

Eg:


query {
    a {
        a
        b
    }
    ...QueryFragment
}

fragment QueryFragment on RootQueryType {
    a {
        b 
        c
    }
}

will get translated to:

[
    'query',
    'query.a',
    'query.a.a',
    'query.a.b',
    'query.a.c',
]

When a field is aliased though, gql will resolve that multiple times, so its added multiple times.

EG:

query {
    a {
        a
        b
    }
    ...QueryFragment
}

fragment QueryFragment on RootQueryType {
    b: a {
        b
        c
    }
}

will be translated to

[
    'query',
    'query.a',
    'query.a.a',
    'query.a.b',
    'query.a',
    'query.a.b',
    'query.a.c',
]

Features:

  • Handles Inline fragments (recursively)
  • Handles normal Fragments (recursively)
  • Handles aliases
  • Returns the paths as many times as they are resolved - a field's path will only be added as much as it will be resolved.
  • 0 dependencies
  • Enforces a maximum field depth (handy if you don't want people querying too much data)
  • Enforces a maximum fragment depth (mostly since its recursive)

TODO:

  • Consider supporting skip directives.