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

subgraphql

v0.0.0-rfc.34

Published

### A Tool to easily launch subgraph flavoured graphql servers via graphql-yoga

Downloads

113

Readme

@windranger-io - subgraphql

A Tool to easily launch subgraph flavoured graphql servers via graphql-yoga

SubgraphQL is a tool that helps convert GraphProtocol subgraph-style schema.graphql files into functional graphql-yoga servers.

Simply provide the content of your subgraph's schema.graphql and a valid entities object, and subgraphql will expose the resultant GraphQL schema as a server. It can be used in either a Node.js environment or as a Next.js endpoint.

Getting started

  • Install subgraphql:

    $ yarn add subgraphql
  • Import subgraphql:

    import { createSubgraph } from 'subgraphql'
  • Construct your schema and 1:1 mapped entities:

    const schema = `
      # id = \`\${owner}\`
      type Name @entity {
        id: ID!
        name: String
        owner: Bytes
        number: BigNumber
      }
    `
    const entities = {
      Name: [
        {
          id: '0',
          name: 'grezle',
          owner: '0x0...',
          number: '0848293943825030',
        },
      ],
    }
  • Setup graphql-yoga with subgraphql and expose as a server (example):

    import * as http from 'http'
    
    const subgraph = createSubgraph({
      schema,
      entities,
      name?: ``, // follow graphprotocol naming - `/subgraphs/name/${name}/graphql`
      graphqlEndpoint?: ``, // override name and set the full graphqlEndpoint uri
      defaultQuery?: `
        {
          names {
            id
            name
            number
            owner
          }
        }`
    });
    
    const server = http.createServer(subgraph)
    
    server.listen(4001, () => {
      console.info('Server is running on http://localhost:4001/api/graphql')
    })

    * Start subgraphql with node:

    $ node ./[filename].js
  • Or expose as a next.js endpoint (example):

    import type { NextApiRequest, NextApiResponse } from 'next'
    
    export default createSubgraph<NextApiRequest, NextApiResponse>({
      schema,
      entities,
      graphqlEndpoint: `/api/graphql`, // this _must_ match the current route
      defaultQuery: `
        {
          names {
            id
            name
            number
            owner
          }
        }`,
    })

    * Start next.js as normal:

    $ yarn dev

Checkout the examples directory for more details...