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

@acastellon/graphql

v1.2.1

Published

GraphQL (HTTPS) based in Express

Readme

@acastellon/graphql

GraphQL (HTTPS) interface based in Express + express-graphql + @graphql-tools/schema.

Note: express-graphql is deprecated (last release 0.12). Consider migrating to graphql-http or Yoga in future updates for this module. The schema loading supports a directory of .graphql + .resolvers.js files plus base _.* files.

See config templates for SERVER and AUTH setup (requires certs for HTTPS).

Usage

const SERVER = require('./config.server.js');
const AUTH = require('./config.auth.js'); // Auth now includes header sanitization + mTLS service auth (security hardening)
const graphql = require('@acastellon/graphql')(SERVER, AUTH);
graphql.run(() => { console.log('GraphQL server running'); });

API / Module surface

Constructor returns { run(cb?) }.

  • run(cb): Starts the HTTPS server (assumes CERTIFICATION_PATH). Listens on SERVER.PORT or process.env.PORT.

Internally loads schemas via ./api.js (merges base _.graphql + directory *.graphql + corresponding * .resolvers.js using Object.assign).

The returned model from api.js is { schema, resolvers } passed to graphqlHTTP.

Minimal example (self-contained):

const SERVER = {
  CERTIFICATION_PATH: '/path/to/certs',
  PORT: 4000,
  WHITELIST: './whitelist',
  SCHEMA_PATH: './schema'  // directory with .graphql + .resolvers.js
};

const AUTH = require('./config.auth.js'); // Auth now includes header sanitization + mTLS service auth (security hardening)

const graphql = require('@acastellon/graphql')(SERVER, AUTH);

graphql.run(() => {
  console.log('GraphQL server is running at https://localhost:4000');
});

License

MIT