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

@prisma-to-graphql/fetch-graphql

v0.3.0

Published

Typed and autocomplete supported fetching for the following:

Downloads

281

Readme

@prisma-to-graphql/fetch-graphql

Typed and autocomplete supported fetching for the following:

  • resolvers
  • resolver arguments
  • resolver outputs
  • field selection
  • aliased outputs

Part of the prisma-to-graphql suite. As such, the expected inputs for this package to work are generated from the prisma-to-graphql package.

Install

npm i @prisma-to-graphql/fetch-graphql

You'll likely want to also install the prisma-to-graphql package to generate the outputs necessary for this package. See the README in prisma-to-graphql on how to setup and use that package.

Usage

The heart of the operation, and possibly the only thing you'll need to use from this package, is the exported createGraphqlFetcher function. This function requires two (typically generated from prisma-to-graphql) inputs to inform if about the shape of your GraphQL schema, and returns a fetchGraphql function. All inputs to the resulting fetchGraphql function are typed:

import {OperationType} from '@prisma-to-graphql/core';
import {createGraphqlFetcher} from '@prisma-to-graphql/fetch-graphql';

/**
 * Both `Resolvers` and `schemaOperationTypeNames` will be generated from the `prisma-to-graphql`
 * package.
 */
import {Resolvers, schemaOperationTypeNames} from '../schema-output.mock.js';

const fetchGraphql = createGraphqlFetcher<Resolvers>(schemaOperationTypeNames);
export type FetchGraphql = typeof fetchGraphql;

async function getUsers(fetchGraphql: FetchGraphql) {
    const users = await fetchGraphql(
        {
            operationType: OperationType.Query,
            operationName: 'MyOperation',
            url: 'https://example.com/graphql',
        },
        {
            Users: [
                {
                    args: {
                        where: {
                            role: {equals: 'user'},
                        },
                    },
                    select: {
                        items: {
                            firstName: true,
                            lastName: true,
                            role: true,
                        },
                    },
                },
            ],
        },
    );

    console.info(users);
}

await getUsers(fetchGraphql);

The fetchGraphql output of createGraphqlFetcher is intended to be reused multiple times and passed around to wherever needs to fetch GraphQL data with the same schema. That being said, there's also no harm in calling createGraphqlFetcher itself multiple times.