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

graphql-reason

v0.1.0

Published

Unofficial port of graphql-js

Readme

graphql-reason: ReasonML/OCaml port for graphql-js

Goal

Focus on creating parser and related tests. Do others later.

FAQ

Why didn't you bind the graphql-js and create the port?

graphql-reason project was born almost right after I released the 0.1.x version of ReasonQL. At first, I thought it was impossible to create GraphQL type-generation library with ppx. But before long, I realized that I was wrong.

But the problem is that we don't have decent port of official graphql-js. graphql_ppx doesn't compile schema files. reason-graphql and ocaml-graphql-server don't parse interface.

So, I decided to create my own library.

Why are you using ReasonML? Not OCaml?

Personally, I'm more familiar with ReasonML than OCaml.

And GraphQL is more frontend-y than backend-y. And frontend developers are more familiar with ReasonML and OCaml.

So, to make it easy for them to participate, I decided to use ReasonML.

Why aren't you using OCamllex and Menhir?

First of all, I'm not familiar with it, unfortunately.

Second, we're not making something new from scratch. We have proven robust code we can copy. Then, when GraphQL spec changes, we don't have to change our own code base and write code based on official library.