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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@gnarlycode/react-route-fetch

v1.1.0

Published

# React Route Fetch

Downloads

6

Readme

GNARLY CODE Production Introducing

React Route Fetch

Helps with fetching data for universal app using react-router with react-router-config.

Installation

npm i --save @gnarlycode/react-route-fetch

Usage

How to define your routes:

// Fetchers should return promises, so we can wait they resolving for ssr
const fetcher = (context, match) => new Promise((resolve) => {
  // Fetch things, save them to store (context) and
  resolve()
})

// Add fetcher to `fetchData` field when defining your `react-router-config`
export const routes = [
  {
    //...
    fetchData: fetcher
  }
]

Wrap client root component with withRouteFetch and it will fetch new data when history changes:

import { renderRoutes } from 'react-router-config'
import { withRouteFetch } from '@gnarlycode/react-route-fetch'

export const ClientRoot = withRouteFetch(routes)(() => renderRoutes(routes))

You should provide a context for data:

// ..
import { routes } from 'routes'
import { createStore } from 'yourStore'
import { ClientRoot } from 'ClientRoot'

// We need to create data context. Redux store, for example
const store = createStore()

hydrate(
  <Provider store={store}>
    <BrowserRouter>
      <ClientRoot fetchContext={store} />
    </BrowserRouter>
  </Provider>,
  document.getElementById('root'),
)

So let's look how to build server:

//...
import { routes } from 'routes'
import { getDataFetchers } from '@gnarlycode/react-route-fetch'

const server = async (req, res) => {
  // Use getDataFetchers to fetch data to store on server before render
  const store = createStore()
  await getDataFetchers(url, routes, store)

  // Then render your app
  renderToString(
    <Provider store={store}>
      <StaticRouter location={req.url} context={routerContext}>
        {renderRoutes(routes)}
      </StaticRouter>
    </Provider>
  )
}

Well Done!

Author: Dmitry Podlesny