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

apollo-error-catcher

v1.0.3

Published

Used as higher order component to catch apollo graphql error in a generic manner

Downloads

2

Readme

apollo-error-catcher

It is used as higher order component to catch apollo graphql error in a generic manner.

Usage:

It is to wrap the react component which is using apollo-react to call graphql query. If there is any unhandled apollo error, it would catch the error and return a component which is readable for user instead of a red error page.

Installation:

You could install this package via following command

npm install apollo-error-catcher

Example:

We need to prepare our own Error Component for unhandled apollo error case.

import React from 'react';

class NotFound extends React.Component {
    render() {
        return (
            <p>not found</p>
        )
    }
}

export default NotFound;

In our react component which is using react-apollo to query. We import catchGraphqlError from apollo-error-catcher and the error component we have made above. We would wrap our component by catchGraphqlError

import React from 'react';
import PropTypes from 'prop-types';
import {connect} from 'react-redux';
import {compose, graphql} from 'react-apollo';
import gql from 'graphql-tag';
import {testAction} from '../../actions/testAction';
import catchGraphqlError from 'apollo-graphql-error'
import {NotFound} from '../Error';

class About extends React.Component {

    static propTypes = {
        email: PropTypes.string,
        isTested: PropTypes.bool,
        testAction: PropTypes.func
    };

    constructor(props) {
        super(props);
    }
    
    render() {
        return (
            <div>
                {!this.props.data.loading && <p>{this.props.data.findUserByEmail.email}</p>}
            </div>
        )
    }
}

const getUserQuery = gql`
    query($email:String!)  {
        findUserByEmail(email: $email) {
            _id
            email
        }
    }
`;

const getUser = graphql(getUserQuery, {
    options: (ownProps) => {
        return {
            variables: {
                email: ownProps.email,
            }
        }
    }
});

const mapStateToProps = (state) => ({
  ...
});

const mapDispatchToProps = (dispatch) => ({
  ...
});

export default compose(
    getUser,
    connect(mapStateToProps, mapDispatchToProps)
)(catchGraphqlError(About, NotFound));

In case there is any error returned, e.g. network error. Error component would be shown instead