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

@gramps/data-source-base

v1.0.0

Published

Base modules for a GrAMPS GraphQL data source.

Downloads

14

Readme

GrAMPS GraphQL Data Source Base

Build Status Maintainability Test Coverage npm version Greenkeeper badge

This is a minimal example and boilerplate for a GrAMPS data source. Inside, you’ll find:

  • Context — an object with methods to retrieve/modify data from the data source (e.g. a CRUD wrapper)
  • Schema — type definitions for GraphQL to interpret the data (see the GraphQL docs on schemas)
  • Resolvers — functions to map the results of calls to model methods to the schema
  • Mock Resolvers — mock functions for offline development

Each file contains a TODO comment explaining the changes you’ll need to make to create a working data source.

The goal of this repo is to provide enough code to allow a working example of a data source and its related tests, but to limit how much boilerplate needs to be edited to get your own data source implemented.

Code Quality and Continuous Integration

To help ensure a reliable, easy-to-maintain data source, this example also includes:

  • Configuration for Travis CI (for automated testing) and Code Climate (for quality analysis)
  • Starts you off right with test coverage at 💯
  • Provides testing helpers for common resolver testing patterns
  • Comes with docs! https://ibm.biz/graphql-data-source

Quickstart

NOTE: Replace all instances of YOUR_DATA_SOURCE_NAME with the actual name you want to use (e.g. data-source-companyname-datatype).

# Get a copy of the data source
npx degit gramps-graphql/data-source-base data-source-YOUR_DATA_SOURCE_NAME

# Move into it
cd data-source-YOUR_DATA_SOURCE_NAME/

# IMPORTANT: Make sure to edit the name, description, contributors, and 
# repository fields in package.json

# Install dependencies
yarn

# Start the dev server
yarn dev

You'll see a message with URLs for the GraphQL gateway and the GraphQL Playground. Open the Playground link (usually http://localhost:8080/playground if you don’t already have something running on port 8080), then run a query:

{
  getById(id: 123) {
    id
    name
    lucky_numbers
  }
}

To Develop with Mock Data

Start the app with the following command:

# Start the gateway with mock data
yarn dev --mock

Notes for Developers

Currently, there is no watch capability (PRs welcome!), so the service needs to be stopped (control + C) and restarted (yarn dev) to reflect new changes to the data source.