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

rest-graphql

v1.0.6

Published

Middleware for Express to adapt REST requests to GraphQL queries

Downloads

87

Readme

rest-graphql

Middleware for Express to adapt REST requests to GraphQL queries

NPM

Motivation

  • You've built a GraphQL server, and it's ready to use.
  • Not all your clients speak GraphQL. At the very least, legacy mobile clients can't make GraphQL requests.
  • You don't want to support both legacy and GraphQL client/server contracts simultaneously

rest-graphql provides middleware that lets you define mappers from REST requests to graphql queries that fetch the same data, letting you normalize all client queries into something your GraphQL server can handle.

Quick Start

Install the package

npm install --save rest-graphql

Let's say you're building out a new profile page and have defined a GraphQL schema for it.
You can fetch the necessary data via:

query PresidentQuery {
  presidents {
    name
  }
}

Create a new RestAdapter and add the middleware to your express server:

import RestAdapter from 'rest-graphql';

/* Build a new adapter
 *
 * isError        - Detect is the graphql query has failed.
 * transformError - Transform the failed query response into a RestAdapterResponse.
 *
 */
const adapter = new RestAdapter({
  isError:         (response) => !!response.errors,
  transformError:  (response) => response.errors[0].__http_secret__,
});

/* Add endpoints to the adapter:
 *
 * path             - The REST endpoint.
 * getQuery         - Function returning a Graphql query as a String.
 * transformSuccess - Transform the successful query response into a RestAdapterResponse.
 */
adapter.addEndpoint({
  path: '/presidents',
  getQuery: (request) => PRESIDENTS_QUERY,
  transformSuccess: response => ({ status: 200, body: response.presidents }),
});

const graphql = express();

graphql.use(adapter.app);
graphql.use('/graphql', graphqlExpress(/* ... */));

Which would result in:

1. HTTP Request:

GET https://api.test.com/presidents

2. Graphql Query:

query PresidentQuery {
  presidents {
    name
  }
}

3. Graphql Response:

{
  presidents: [
    { name: "Jacques Chirac" },
    { name: "George Washington" }
  ]
}

4. HTTP Response:

["Jacques Chirac", "George Washington"]

Error Handling

To transform Graphql query errors into the REST responses we recommend using something similar to apollo-server formatError options. In the above example we format the HTTP errors like the following:

{
  "presidents": null,
  "errors": [
    {
      "message": "Internal server error",
      "__http_secret__": {
        "status": 500,
        "body": {
          "message": "Internal server error"
        }
      },
    },
  ]
}