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

@graphql-detective/urql

v0.2.1

Published

<h1 align="center">@graphql-detective/urql</h1>

Readme

Installation

pnpm add @graphql-detective/urql

or

npm i @graphql-detective/urql

or

yarn add @graphql-detective/urql

When constructing your urql client, add detectiveExchange as a last exchange in the chain right before fetchExchange:

import { detectiveExchange } from '@graphql-detective/urql'
import { Client, Provider, fetchExchange } from 'urql'

// ...

const client = new Client({
    url: 'endpoint_url',
    exchanges: [detectiveExchange, fetchExchange],
})

// ...
// Pass down the client to the urql provider (differs by framework)
// <Provider client={client}>

Tracking

After graphql-detective is correctly plugged into your exchange chain, it will start tracking every single query and mutation that is being executed.

Please note, usage records are sourced directly from accessing properties at runtime. This means that if somewhere in your code you conditionally access a field, it will be tracked as used only if the condition is met. This is why for complex setups it is recommended to either go through a user flow or run an automated test with the tracking enabled.

After you feel like you have recorded enough, you can access unused records by calling the following function in the browser console:

$unusedQueryFields.get()

You can also access usage records and parsed GQL documents with

$queryStore.get()
$usageStore.get()

That is only temporary and will be replaced with a more user-friendly interface in the future.