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

@pocket-tools/apollo-utils

v3.13.2

Published

Utilities for apollo implementing services

Downloads

13,883

Readme

Apollo Utilities

We use this repository as a place to keep code we use across our apollo implementing services' repositories. These include plugins, dataloader functions, etc.

Development

  1. npm install
  2. npm run test run tests or npm run test:watch to watch files and run tests when the code changes.
  3. Be sure to export any new modules in src/index.ts

Dependency

  1. Update the apollo server version to 3 and node version to 16 to import this package.

Example Usage

Sentry Plugin and Error Handler

  • Setting up plugin and error handler with the apollo server
const server = new ApolloServer({
  schema: buildFederatedSchema({ typeDefs, resolvers }),
  plugins: [sentryPlugin],
  formatError: errorHandler,
});
  • Throwing custom error
throw new NotFoundError('book id');
  • Throwing Apollo errors
import { UserInputError } from 'apollo-server-errors';

throw new UserInputError('Invalid User Input');

ISOString Scalar

This gives you a ISOString Scalar that expects a valid TypeScript Date object or null (to represent no date && cases like 0000-00-00) on the serverside, and an ISO-8601-compliant Datetime string or an empty string when interacting with clients.

The expectation of this custom scalar is that the database client layer will handle mapping valid Dates to a Typescript Date Object and invalid Dates to either null (e.g. should be considered a None type) or throw some internal error.

This custom scalar expects UTC, ISO-8601-compliant datetime string values as input only. Inputs must specify UTC and must follow ISO-8601.

In your graphql schema file:

"""
ISOString scalar - all datetimes fields are Typescript Date objects on this server &
returned as ISO-8601 encoded date strings (e.g. ISOString scalars) to GraphQL clients.
See Section 5.6 of the RFC 3339 profile of the ISO 8601 standard: https://www.ietf.org/rfc/rfc3339.txt.
"""
scalar ISOString

type Something {
  """
  Timestamp that the Something entity was created.
  """
  createdAt: ISOString

  """
  Timestamp that the Something entity was deleted, null if not deleted.
  """
  deletedAt: ISOString
}

In your types file (if not autogenerated), anything that is an ISOString is either Date or Date | null (if the field is optional):

export type Something = {
  createdAt: Date;
  deletedAt: Date | null;

In your resolvers file(s):

import { PocketDefaultScalars } from '@pocket-tools/apollo-utils';

const resolvers = {
  ...PocketDefaultScalars,
  // ...other resolvers...
  // if another server needs a different internal representation
  // they can still override the defaults below:
  // ISOString: someNonDefaultScalar
};

& make sure the server typeDefs points back to the schema.graphql file already update (in order to know about the ISOString type).