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

react-apollo-composer

v1.0.3

Published

react apollo composer for queries and mutations

Readme

react-apollo-composer

react apollo composer for queries and mutations

NPM

Install

npm install --save react-apollo-composer
yarn add react-apollo-composer --save

Usage

import React from 'react';
import gql from 'graphql-tag';
import Queries from 'react-apollo-composer';

const GET_ME = 'getMe { name }';
const GET_WEATHER = 'getWeather { temperature, unit }';

const Example = () => (
  <Queries queries={{ me: GET_ME, weather: GET_WEATHER }}>
    {({ me, weather, _loading, _hasError }) => {
        if (_loading) return <p>Loading...</p>;
        if (_hasError) return <p>Error :(</p>;

        return (
          <div>
            <p>Hello, { me.data.name }</p>
            <p>It's {weather.data.temperature}°{weather.data.unit}</p>
          </div>
        )

    }}
  </Queries>
);

Property queries is an object that can accept graphql query and mutation. The child element, will be called with the rendered query and mutation, and few extra variable:

  • _loading : true if one of the query is loading
  • _error : combine all error variable from each query to one array
  • _hasError : true if one of the query has an error

Why

Because it is much more cool than:

import React from 'react';
import gql from 'graphql-tag';
import { Query } from 'react-apollo';

const GET_ME = 'getMe { name }';
const GET_WEATHER = 'getWeather { temperature, unit }';

const Example = () => (
  <Query query={GET_ME}>
    {({ loading, error, data }) => {
        if (_loading) return <p>Loading...</p>;
        if (_hasError) return <p>Error :(</p>;

        return (
          <div>
            <p>Hello, { data.name }</p>
            <Query query={GET_WEATHER}>
              {({ loading, error, data }) => {
                  if (_loading) return <p>Loading...</p>;
                  if (_hasError) return <p>Error :(</p>;

                  return (
                    <p>It's {data.temperature}°{data.unit}</p>
                  )

              }}
            </Query>
          </div>
        )

    }}
  </Query>
);

And easier than (even if react-adopt is super cool):

import React from 'react';
import gql from 'graphql-tag';
import { Query } from 'react-apollo';
import { adopt } from 'react-adopt';

const GET_ME = 'getMe { name }';
const GET_WEATHER = 'getWeather { temperature, unit }';

const Compose = adopt({
  me: ({ render }) => <Query query={GET_ME}>{render}</Query>,
  weather: ({ render }) => <Query query={GET_WEATHER}>{render}</Query>,
});

const Example = () => (
  <Compose>
    {({ me, followers }) => {
        if (me.loading || weather.loading) return <p>Loading...</p>;
        if (me.error || weather.error) return <p>Error :(</p>;

        return (
          <div>
            <p>Hello, { me.data.name }</p>
            <p>It's {weather.data.temperature}°{weather.data.unit}</p>
          </div>
        )

    }}
  </Compose>
);

I use react-adopt in this library and in some case it might fit better your requierement.

License

MIT © [Alexandre Piel]