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

@mishguru/graphqldir

v4.0.0

Published

Package modularized apollo-server schema

Downloads

3

Readme

GraphQLDir

This is a fork of Saturn-GQL.

Install

npm i @mishguru/graphqldir

Has your GraphQL api code grown out of control? Does your GraphQL api sit in a single file with thousands of lines of code? Unsure of the best way to logically separate it all? GraphQLDir is here to help!

GraphQLDir takes care of packaging up your modularized graphql-tools schema, allowing you to separate your types, queries and mutations into logical groupings.

To get started, you'll need to split your graphql api into a directory structure similar to the diagram below. If you are already using graphql-tools this should be a fairly trivial step.

graphql
  group1
    index.js
  group2
    index.js
  group3
    index.js

Each index file can export the following properties:

  • resolvers
  • queries
  • mutations
  • subscriptions
  • type
  • typeQuery
  • typeMutation
  • typeSubscription

To Use

import { makeExecutableSchema } from 'graphql-tools'

import GraphQLDir from '@mishguru/graphqldir';
const graphqldir = new GraphQLDir(`${__dirname}/graphql`);

// Graphql Schema
const schema = makeExecutableSchema(graphqldir.makeSchema());

// just types
const types = graphqldir.createTypes();

// just resolvers
const resolvers = graphqldir.createResolvers();

Note that graphql-tools is not a dependency of this library. This is to avoid any duplication or version misatches of the graphql package.

File layouts

Each directory should have an index.js or index.ts file.

You can also split up the definitions into multiple files, like so:

- index.js
- queries.js
- mutations.js
- type.js

Types

This string is copied as-is into the schema types.

export const type = `
  type Author {
    id: Int!
    firstName: String
    lastName: String
    posts: [Post] # the list of Posts by this author
  }

  type Post {
    id: Int!
    title: String
    author: Author
    votes: Int
  }
`;

Query Types

This is used to define fields on the "RootQuery" type.

export const typeQuery = `
  posts: [Post]
  author(id: Int!): Author
`;

Mutation Types

This is used to define mutations.

export const typeMutation = `
  upvotePost(postId: Int!): Post
`;

Subscription Types

This is used to define subscriptions.

export const typeSubscription = `
  postAdded: Post
`;

Resolvers

This is used to implement the resolving functions for any types.

export const resolvers = {
  Author: {
    posts: author => filter(posts, { authorId: author.id }),
  },
  Post: {
    author: post => find(authors, { id: post.authorId }),
  },
};

Queries

This is used to implement the RootQuery field resolvers.

export const queries = {
  posts: () => posts,
  author: (_, { id }) => find(authors, { id }),
};

Mutations

This is used to implement the Mutation handlers.

export const mutations = {
  upvotePost: (_, { postId }) => {
    const post = find(posts, { id: postId });
    if (!post) {
      throw new Error(`Couldn't find post with id ${postId}`);
    }
    post.votes += 1;
    return post;
  },
};

Subscriptions

This is used to implement the Subscription handlers.

export const subscriptions = {
  postAdded: {
    subscribe: () => ({
      async next() {
        const post = await waitForPostToBeCreated()
        return {
          value: post,
          done: false
        }
      },
      async return() {
        return {
          value: undefined,
          done: true
        }
      },
      async throw(error) {
        throw error
      },
      [Symbol.asyncIterator]() {
        return this
      }
    })
  },
};

License

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.