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 🙏

© 2026 – Pkg Stats / Ryan Hefner

readiness-gql

v1.0.0

Published

GraphQl schema and server for readiness services

Readme

Readiness Graphql Server

The repo will be serving as a single middleware for all frontend apps to query Readiness services.

Requirements:

  1. node >= 10.0.0
  2. npm >= 6.4.0

Preferred node 12

nvm use 12

How to develop in the repo:

  1. master branch is the head branch. every commit needs to be merged through a PR to be approved by 2 reviewers at least.
  2. Define your schema in src/schemas directory. use .schema file for defining and extending the schema.
  3. Export your schema through index.ts files for corresponding division. (if you are defining new schema division, import and define that in schemas/index.ts)
  4. To define the types and resolvers types for your schema, do

    npm run generate

  5. To write resolvers, check src/resolvers. use the same directory structure as schemas for readability.
  6. right now resolvers --depends-upon--> data-loaders --depends-upon--> apiClients. (refer to the same guide)
  7. Refrain yourself from coding with anytype or in nodeJs directly. use strict types everywhere with typescript.
  8. Define default values for your environment variables in .env file(this will ignored while pushing to repo.) in the defined format below:
     NODE_ENV="development"
     MOCK="true"
     CONTENT_ENGINE_URL="http://ce.internal.checklist.mindtickle.com:80"

How to build the repo:

npm run build

If NODE_ENV="development", webpack hot reloading will be automatically enabled. Then in a new shell, run the following

How to run the built code:

npm run start

Server should start at : http://localhost:4000/graphql

Sample query

fragment value on ConfigValue{
  ... on BoolValue{
    boolValue
  }
  ... on StringValue{
    stringValue
  }
}
fragment config on Config{
	key,
  value{...value}
}

fragment request on Request{
  method,
	host,
	pathname,
	headers{...config},
	query{...config},
	params{...config},
  ... on PostRequest{
    body{...config}
  }
}
query{
  widget{
    listDataSources(pagination:{from:0,size:10}){
      total
      data{
        id
        request{...request}
      }
    }
  }
}

Sample Mutation

mutation($input:DataSourceInput!){
  dataSource{
    createDataSource(input: $input){
      name,
      isActive
    }
  }
}

# Query Variables - 
{
  "input":{
    "name": "data1",
    "request": {
      "host": "https://mindtickle.com/",
      "method": "GET",
      "pathname": "graphql"
    }
  }
}
  

How to run the tests in repo:

npm run test

How to temporarily supress audit vunrabilities

package.json scripts => audit change to

node node_modules/better-npm-audit audit -i 1179

Troubleshooting

Invalid regular expression: /${(?[A-Z0-9_]+)(:((?[^:]+)|("(?[^"]+)")))?}/: Invalid group

Check node version. Use node >= 10.0.0

nvm use 12