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

react-middleware-router

v0.1.4

Published

A middleware-based router for React

Downloads

65

Readme

react-middleware-router

A middleware-based router for React.

Installation

npm install react-middleware-router

Usage

This router is designed to be a drop-in replacement for both react-router and if using redux react-router-redux.

Browser Routing

Here is an example of a small app:

const { BrowserRouter, Route, Switch } = require('react-middleware-router')

class App extends Component {

  render() {
    return (
      <BrowserRouter history={history}>
        <Switch errorComponent={NotFound} loadingComponent={Spinner}>
          <Route path="/bar" middleware={[barware]} component={Bar} />
          <Route path="/baz" middleware={[bazware]} component={Baz} />
          <Route path="/foo" middleware={[fooware]} component={Foo} />
          <Route exact path="/" component={Home} />
        </Switch>
      </BrowserRouter>
    )
  }
}

Notice a few additions:

  • errorComponent is optionally supplied to Switch. There is no need to create a "catch-all" route for errors.
  • loadingComponent is optionally supplied to Switch. This enables an app-wide loading/spinner component which is rendered until the route with middleware has completeing processing the middleware.
  • middleware is optionally supplied to Rotue. This is an array of functions which run before the component for the route is rendered. If any middleware return an error the errorComponent is rendered instead.

Browser Routing with Redux

const { ConnectedRouter, Route, Switch } = require('react-middleware-router')
const { Provider } = require('react-redux')

class App extends Component {

  render() {
    return (
      <Provider store={store}>
        <ConnectedRouter history={history}>
          <Switch errorComponent={NotFound} loadingComponent={Spinner}>
            <Route path="/bar" middleware={[barware]} component={Bar} />
            <Route path="/baz" middleware={[bazware]} component={Baz} />
            <Route path="/foo" middleware={[fooware]} component={Foo} />
            <Route exact path="/" component={Home} />
          </Switch>
        </ConnectedRouter>
      </Provider>
    )
  }
}

Middleware

Here is an exampe of a middleware function:

function bazware(o, next) {
  setTimeout(function() {
    next()
  }, 250)
}
  • The first argument, property o, is the object that was optionally passed from a previous middleware.
  • The second argument, function next, is the callback to tell the middleware it has completed (or errored).
  • The first argument to next is always an error or null.
  • The second argument to next is the data you want to pass to the next middleware.

Passing data or errors to middleware

Data

next(null, {some: 'data'})

Error

next({some: 'error'})