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

@therobot/api-schema-directives

v0.0.2

Published

some apollo directives

Downloads

3

Readme

@therobot/api-schema-directives

I am not sure if storing directives in separate package is a good idea.

There is not much docs on using directives in apollo-federation, so i am useing them like this, in every federated endpoint i need them

Usage

const { ApolloServer, gql } = require('apollo-server-cloud-functions')
const { buildFederatedSchema } = require('@apollo/federation')
const { attachDirectiveResolvers } = require('graphql-tools')

const typeDefs = gql`
  directive @auth on FIELD_DEFINITION
  extend type Query {
    me: Account @auth
  }
`

const resolvers = { Query: { me: () => 'secure' } }
const jwtHandler = require('@therobot/jwt-handler')
const context = ({ req }) => {
  const jwt = jwtHandler(req.headers['authorization'])
  return { jwt }
}

const directiveResolvers = require('@therobot/api-schema-directives')
const schema = buildFederatedSchema([{ typeDefs, resolvers }])
attachDirectiveResolvers(schema, directiveResolvers)

const server = new ApolloServer({
  schema,
  playground: true,
  introspection: true,
  context,
})

exports.handler = server.createHandler()

Auth, custom handlers

Define directive with some arguments

# `role` argument is defined as array
directive @auth(role: [String]) on FIELD_DEFINITION

extend type Query {
  # brakets can be ommited
  me: Account @auth(role: "account")
}

And make a handler in context

const context = ({ req }) => {
  const jwt = jwtHandler(req.headers['authorization'])
  return {
    jwt,
    onAuthRole: (jwtRole, directiveRole) => {
      return directiveRole.includes(jwtRole)
    },
  }
}

field will not be resolved if JWT have no field that matches argumentName directive was called with.

@auth(argumentName: "value")

field will not be resolved if handler is not defined,

onAuthArgumentName: () => true


telegram