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

@earnest-labs/microservice-chassis-apollo

v0.1.0

Published

A microservice-chassis plugin that provides apollo server functionality

Downloads

284

Readme

microservice-chassis-apollo

An MC plugin for apollo graphql support.

This plugin in turn loads its own plugins to allow you to produce a modularized graphql schema.

An example of a graphql schema module can be found here

Getting Started

microservice-chassis-apollo is intended for use, unsurprisingly enough, with microservice-chassis:

npm i --save @earnest-labs/microservice-chassis @earnest-labs/microservice-chassis-apollo

At this point, you should be able to see the Apollo GraphQL Explorer, which will include a ping Query

% npx chassis-start &

% open http://localhost:3000/graphql

% curl 'http://localhost:3000/graphql' -X POST \
  -H 'Content-Type: application/json; charset=utf-8' \
  -H 'Origin: http://localhost:3000' \
  --data-raw '{"query":"query Query {ping {name version}}","variables":{},"operationName":"Query"}'
{"data":{"ping":{"name":"your-project-name","version":"0.0.1"}}}

To create a GQL schema module, define a typescript module, with a name matching *.apollo.ts, that has a default export conforming to the ApolloChassisPluginBuilder type. This type is an async function that takes a PluginContex (defined in @earnest-labs/microservice-chassis) and returns an ApolloChassisPlugin

You may have as many GQL schema modules as you like, though if they contain conflicting information, like re-using type names, your service will likely fail to start. Coordinating type, query, and mutation names is up to you.

Details On ApolloChassisPlugin

The current definition is in src/apollo.chassis-plugin.ts, and looks something like this:

export interface ApolloChassisPlugin {
    name: string;
    version: string;

    types?: string[];
    queries?: string[];
    mutations?: string[];
    resolver?: {
        Query?: Object,
        Mutation?: Object
    }
}

As you can see, most of the entries are optional.

types is a collection of graphql strings representing the types in your schema, e.g.:

result.types = [
  `type SomeModel {name: String, version: String, field: Int}`,
  `type AnotherModel {id: Int, name: String, value: String}`
]

queries is a collection of graphql strings representing entries in the Query object. An example entry might look like this:

result.queries = [
  'model: SomeModel',
  'anotherModel: AnotherModel'
]

mutations is a collection of graphql strings representing entries in the Mutation object. An example entry might look like this:

result.mutations = [
  'updateModel(name: String, field: Int) : Model',
  'updateAnotherModel(id: Int, value: String): AnotherModel'
]

resolver is an Apollo resolver object, with a Query subobject to deal with entries in queries, and a Mutation subobject to deal with entries in mutations. For example:

result.resolver = {
  Query: {
    model: async() => ({name: "hardcoded-name", version: "hardcoded-version", field: 42}),
    anotherModel: async() => ({id: 42, name: "hardcoded-name", value: "hardcoded-value"}),
  },
  Mutation: {
    updateModel: async(_, {name, field}) => ({name, version: "hardcoded-version", field}),
    updateAnotherModel: async(_, {id, value}) => ({id, name: "hardcoded-name", value}),
  }
}