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

graphile

v5.0.0

Published

Swiss army knife for dealing with all things Graphile

Downloads

3,153

Readme

graphile

Graphile makes a number of open source projects, some of the headline projects include PostGraphile, Graphile Worker, Graphile Migrate and Grafast, but there are many others. This module is intended to be a CLI that will help when interacting with these various projects, helping you to create, debug, update, interact with and maintain them.

At the moment, it doesn't contain much, but it should grow over time.

graphile config

Config debugging commands

graphile config print

Prints out the configuration from your graphile.config.mjs (or similar) file in an easy to read/digest form.

graphile config options

Outputs markdown detailing the full list of options that you may specify in your config file, suitable for inclusion in your repository's documentation folder. Output is honed specifically to your set of plugins and presets.

graphile inflection

Inflection debugging commands

graphile inflection list

Outputs markdown detailing the full list of inflectors that have been defined (and may be overridden via a plugin), suitable for inclusion in your repository's documentation folder. Output is honed specifically to your set of plugins and presets.

graphile behavior

Behavior debugging commands. (WARNING: This hasn't been updated since behavior defaults were reworked, so is now super verbose and a little confusing.)

graphile behavior debug

Lists the entityTypes available to debug (will vary depending on your plugins); example:

$ graphile behavior debug
No entity type was specified; please pick one of the supported entity types:
- pgCodec
- pgCodecAttribute
- pgCodecRef
- pgCodecRelation
- pgRefDefinition
- pgResource
- pgResourceUnique

(See @dataplan/pg registry for details of the example above.)

graphile behavior debug <entityType>

Lists the entity identifiers for that specific entity type; e.g.

$ graphile behavior debug pgResource
No entity identifier was specified; please pick one of the supported entities for entity type 'pgResource':
- fn
- person
- post

graphile behavior debug <entityType> <entityIdentifier>

Outputs the behavior string for the given entity, along with sources that caused it to be derived in that way - indicating which behaviors came from which plugins.

The output for each plugin includes styled text:

  • green text is behavior strings added by this plugin - this may be either at the start or end of the string
  • grey text is inherited from previous behavior string
  • strike through text (green or grey) indicates a behavior fragment that has been overridden by a later value in the string

The __ApplyBehaviors_*__-style entry is a workaround that shows the "multiplication" of the previous behavior with the default behavior. It's a hack/workaround until we have a better way of presenting this concept.

graphile behavior debug <entityType> <entityIdentifier> <filterString>

As above, but pass a filter string (a behavior fragment) and any behaviors related to that will be highlit so you can see what came to manipulate that particular setting.