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

@times-components/schema

v0.7.5

Published

The GraphQL schema that is generated from our GraphQL endpoint is used primarily for two cases, linting and helping out Apollo with a [fragment matcher](https://www.apollographql.com/docs/react/advanced/fragments.html#fragment-matcher).

Downloads

3,752

Readme

Schema

The GraphQL schema that is generated from our GraphQL endpoint is used primarily for two cases, linting and helping out Apollo with a fragment matcher.

This package auto-generates the schema.json necessary for linting at install time (provided you set the GRAPHQL_ENDPOINT envar) and also the fragmentMatcher. By inlining it we can statically bundle the minimal amount of code for the Apollo Client to be happy, with no runtime overhead.

We do this at install time in order to fail the builds as soon as there's a mismatch with our server side implementation.

Usage

Everything should be generated at install time but you can regenerate by running something like:

GRAPHQL_ENDPOINT='my.endpoint.io/graphql' yarn postinstall

Contributing

Please read CONTRIBUTING.md before contributing to this package

Running the code

Please see our main README.md to get the project running locally

Development

The code can be formatted and linted in accordance with the agreed standards.

yarn fmt
yarn lint