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

@nkzw/pothos-locate

v1.0.0

Published

Enables GraphQL go-to-definition by mapping types and fields to Pothos source locations.

Readme

@nkzw/pothos-locate

Enables GraphQL go-to-definition by mapping types and fields to Pothos source locations.

https://github.com/user-attachments/assets/e941950a-2944-4ab8-9954-17c6ad320347

Installation

Install the Relay VS Code extension for VS Code.

Then install the @nkzw/pothos-locate package:

npm install -D @nkzw/pothos-locate

Create a pothos-locate file in the root of your project, run chmod +x pothos-locate, and add the following code:

#!/bin/sh

node_modules/.bin/pothos-locate --src <path to your graphql definitions> "$@"

Now set the relay.pathToLocateCommand in your workspace settings to ./pothos-locate.

Note: We may be able to remove this intermediate file in the future, pending changes to the Relay VS Code extension.

Usage

In VS Code you can cmd+click on a GraphQL type, field, interface, enum, or input object in your Relay GraphQL queries to jump directly to the Pothos implementation of the entity.

Configuration

The package currently supports three configuration options:

  • --src (defaults to the project root): The source directory where your Pothos GraphQL definitions are located. It is recommended to set this to the directory closest to your GraphQL schema for improved performance.
  • --builder (defaults to builder): The local variable name used to define the GraphQL schema with Pothos. Your project must use the same binding name in every module.
  • --extensions (defaults to ts,tsx): The file extensions to search for Pothos definitions.

Troubleshooting

It doesn't work

You can call the script directly to see if it is working correctly. For example, if you have a User type with a displayName field you can run the following command:

./pothos-locate --src <path to your graphql definitions> --builder <your builder variable name> '<projectName>' User.displayName

and it should output the exact location:

/Users/cpojer/Projects/athena-crisis/artemis/graphql/nodes/User.tsx:120:4

Note: The <projectName> is unused in this package but still passed by the Relay VS Code extension. You can use any string here.

It still doesn't work for my codebase

Send a Pull Request or consider a GitHub Sponsorship.