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

@apollo/utils.usagereporting

v2.1.0

Published

Generate a signature for Apollo usage reporting

Downloads

6,845,633

Readme

usageReporting

This package exports the useful bits of usage reporting related to signature computation and referenced field calculation.

usageReportingSignature

In Apollo Studio, we want to group requests making the same query together, and treat different queries distinctly. But what does it mean for two queries to be "the same"? And what if you don't want to send the full text of the query to Apollo's servers, either because it contains sensitive data orw because it contains extraneous operations or fragments?

To solve these problems, Apollo Studio and related components have the concept of "signatures". We don't (by default) send the full query string of queries to Apollo's servers. Instead, each trace has its query string's "signature".

The usageReportingSignature function is a combination of the following transforms:

  • dropUnusedDefinitions: removes operations and fragments that aren't going to be used in execution
  • stripSensitiveLiterals: replaces all numeric and string literals as well as list and object input values with "empty" values
  • removeAliases: removes field aliasing from the operation
  • sortAST: sorts the children of most multi-child nodes consistently
  • printWithReducedWhitespace, a variant on graphql-js's print which gets rid of unneeded whitespace

calculateReferencedFieldsByType

Given a DocumentNode (operation) and a GraphQLSchema, calculateReferencedFieldsByType constructs a record of typeName -> { fieldNames: string[], isInterface: boolean }. This record is the field usage data sent to Apollo Studio keyed by operation signature (usageReportingSignature).