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

@vtex/graphql-utils

v1.5.21-avon.0

Published

GraphQL utilities

Downloads

1,977

Readme

@vtex/graphql-utils

GraphQL utilities to use GraphQL over HTTP with ZERO bundle sizes

Compatibility

This module solves the transport layer of GraphQL queries. For this reason, we only require a babel-friendly environment. Also, many graphql clients are supported. Example of such environments/clients are:

How it works?

This library solves the GraphQL over HTTP problem. This means you need access to both the frontend and the backend to use this library. It has 3 main components: A gql tag and request function to allow you to declare and fetch data from your graphql server in your frontend. A babel plugin to optimize your JS/TS assets so your graphql queries add ZERO bytes to your final bundle. A codegen plugin to generate persisted queries to your persisted query ready graphql server

The main idea behind this module is to preprocess and aggregate all graphql queries of your frontend into a single JSON file. This file is then uploaded to the graphql server so that, when your frontend needs to query any data, it asks for the graphql server to execute a given query, instead of having to send the whole query. This is really similar to Apollo's automatic persisted queries, however, instead of gathering the queries dynamically, we preprocess and upload the queries to the server before we deploy the website. This makes some optimizations possible, like:

  • ZERO bundle sizes
  • Inline Fragments
  • Flattened Transforms
  • Redundant Node Skipping.

Installing

Installing this plugin may vary depending on your setup. The instructions below are recommended if you are using graphql-codegen cli. If you are using graphql-codegen in a different way please refer to their docs on how to add plugins instead.

To install, just

$ yarn add @vtex/graphql-utils

Note. Also make sure to install graphql codegen cli

Adding graphql-codegen

To generate the persisted query file, add this plugin to your codegen config. If you don't have one yet, create a codegen.yml file with the following:

generates:
path/to/persisted.json:
 plugins:
   - @vtex/graphql-utils/codegen

Now, open your terminal and run:

$ yarn run graphql-codegen

This should generate a persisted.json file containing a map between operation names and queries. Use this file o your graphql server to filter and run queries.

Installing on Gatsby

To use it on Gatsby, we need to setup the babel plugin. To do this, we can use Gatsby's onCreateBabelConfig hook on gatsby-node.js file. On this file add the following:

// ...
exports.onCreateBabelConfig = ({ actions }) => {
  actions.setBabelPlugin({
    name: `@vtex/graphql-utils/babel`,
    options: {},
  })
}

Now you should be good to go and create your queries.

Usage

Now that you have successfully installed and configured both babel and codegen plugins, you can start writing your queries. Let's start by declaring the following code:

import { gql, request } from '@vtex/graphql-utils'

const MyQuery = gql`
  query MyQuery { ... }
`

request({ operationName: MyQuery, variables: {} }).then(response => {
  const { data, errors } = response

  console.log('GraphQL data and errors', { data, errors })
})

This code import two helpers from our lib, gql and request. Use the first one to wrap query declarations. Use the result of this expression to feed the operationName parameter of request. That's it! you can use this in most GraphQL Clients, like Apollo Client, SWR, and React Query. Also, this is compatible with your favorite frameworks like Next.JS and Gatsby.

For instance, to use it with SWR, you can declare a useQuery hook:

import { request } from '@vtex/graphql-utils'

const useQuery = ({ operationName, variables }) => useSWR(`/graphql/${operationName}::${JSON.stringify(variables)}`, {
    fetcher: () => request({ operationName }),
  })

and use it on your code like:

import { gql } from '@vtex/graphql-utils'

const MyQuery = qql`
  query MyQuery { ... }
`

const useMyQuery = (variables) => useQuery({ operationName: MyQuery, variables })