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-local-fetch

v2.1.2

Published

Simple lib for fetch

Downloads

57

Readme

React-local-fetch

Simple lib for fetch

example on codesandbox


Notice

This lib intended for react project without hooks

Features

  • handle uniq request id
  • handle un mount state
  • provide default reducer

You can use LocalFetching to...


...if you need to make fetch-request

Usually you do something like the example below:

class Foo extends Component {
  constructor(props) {
    super(props)
    this.state = {
      news: [],
      error: null,
    }
  }

  async componentDidMount() {
    try {
      const news = await fetchNews()

      this.setState({ news })
    }
    catch (error) {
      this.setState({ error })
    }
  }

  render() {
    if (this.state.error) {
      return '...has some error'
    }

    return this.state.news.map(renderer)
  }
}

or with fetch-status state varriable

...
  this.state = {
    ...
    fetch: 'initial'
  }

  async componentDidMount() {
    try {
      this.setState({ fetch: 'loading' })
      const news = await fetchNews()

      this.setState({ news, fetch: 'finish' })
    }
    catch (error) {
      this.setState({ error, fetch: 'fail' })
    }
  }
...

seems like an ordinary example, but if you have more pages and fetch call ? You write a lot of boilerplate code. You might continue use this practic or use local-fetch lib.

With lib (and recompose) example

import { withLocalFetch, isFailed } from 'react-local-fetch'
import { compose, lifecycle } from 'recompose'

// in follow code writed default behavior
const newsReducer = (state = [], action) => {
  switch(action.type) {
    case 'SET': return ({
      ...state,
      data: action.payload,
    }),
    default: return state,
  }
}

const enhance = compose(
  // callback might be a function
  // with type (Props /* initial props */, () => Props /* actual props */)
  withLocalFetch('news', {
    action: apiFn,
    reducer: newsReducer,
  }),
  lifecycle({
    componentDidMount() {
      this.props.news.fetch({
        pageId: 1,
        type: 'SET',
      })
    },
  }),
)


const view = ({ news }) => {
  if (isFailed(news.status)) {
    return '...has some error'
  }

  return news.data.map(renderer)
}