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

@analogculture/graphd

v1.0.1

Published

A conventional schema loader for Apollo GraphQL. Connect your GraphQL servers and schemas together, remotely, locally or a mix of both.

Readme

Graphd

A conventional schema loader for Apollo GraphQL. Connect your GraphQL servers and schemas together, remotely, locally or a mix of both.

Why

Apollo schema stitching is a powerful way to connect domain driven and remote services together into a single query endpoint. This module provides convention for one possible implementation, designed to reduce boilerplate for loading schemas and resolvers.

Usage

Simple

The most basic configuration for graphd loads schemas and resources from a directory resources in your project's root and merges them into a single schema.

const graphd = require('graphd')
graphd.get()

With Joins

Setting join to true will load a join schema and resolvers from the root (by default) of your project. This join schema defines the relations between all other loaded resources up to this point. Multiple remote servers can define joins on the same types but only for resources that have already been loaded. You can use graphd's createDelegate method to define the joins between resources.

const graphd = require('graphd')
graphd.get({ join: true })

Stitch a Remote API

remoteAPI accepts a single string or array of strings with urls for remote GraphQL APIs. e.g.

{ remoteAPI: 'http://localhost:3001' }

{ remoteAPI: ['http://localhost:3001', 'http://localhost:3002'] }

RemoteAPI will continually retry each connection url until a connection can be established. Negating the need to boot services in any particular order.

const graphd = require('graphd')
graphd.get({ join: true, remoteAPI: 'http://localhost:3000' })

Full configuration

graphd.get({
  join: true,
  remoteAPI: ['http://localhost:3000', 'http://localhost:3001'],
  retryTimeout: 5000,
  paths: {
    resources: './resources',
    joinSchema: './schema.gql',
    joinResolvers: './resolvers'
  }
})

Simple Express

All of the above configurations can be used in a server setting.

const express = require('express')
const { ApolloServer } = require('apollo-server-express')
const graphd = require('@analogculture/graphd')

var app = express()

const server = new ApolloServer({
  schema: graphd.get({ join: false, remoteAPI: null })
})

server.applyMiddleware({ app })

app.listen({ port: 3000 }, () => {
  console.log(`Graphql server started on http://0.0.0.0:3000`)
})