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-router-nomatch

v2.0.6

Published

React Router interface that renders a component when no child route is matched.

Downloads

36

Readme

React Router NoMatch

npm

React Router interface that renders a component when no child route is matched.

Why not use Switch?

Switch renders the first child Route that matches and nothing else. This is fine if your app is built as a set of monolithic pages.

NoMatch allows multiple child Routes to be rendered, and lets you specify a fallback component if none of them match. This is more suited to dynamic routing where multiple Routes match the same location (for instance in a responsive master-detail layout where both the master and detail views have their own Routes).

Install

$ npm install --save react-router-nomatch

Props

  • component: The fallback component class. Renders with a match prop that is true if one of the child Routes matched.
  • render: Same as component but for inline rendering. Renders with a match prop that is true if one of the child Routes matched. component takes precedence over render if both are defined.
  • alwaysRender: Whether to always render the fallback component or only when none of the Routes match. Defaults to false.

Example

import React from 'react';
import ReactDOM from 'react-dom';
import { Router, Route, Redirect } from 'react-router-dom';
import { createBrowserHistory } from 'history';
import NoMatch from 'react-router-nomatch';

const Navbar = () => <div>Navbar</div>;
const SignIn = () => <div>SignIn</div>;
const Newsfeed = () => <div>Newsfeed</div>;
const MessagesMaster = () => <div>MessagesMaster</div>;
const MessagesDetail = () => <div>MessagesDetail</div>;
const NotFound = () => <div>NotFound</div>;

const App = () => {
  return (
    <Router history={createBrowserHistory()}>
      <NoMatch component={NotFound}>
        <Navbar />
        <Route path="/signin" exact component={SignIn} />
        <Route path="/" exact render={props => <Redirect to="/signin" />} />
        <Route path="/newsfeed" exact component={Newsfeed} />
        <Route path="/messages" component={MessagesMaster} />
        <Route path="/messages/:index?" exact component={MessagesDetail} />
      </NoMatch>
    </Router>
  );
}

const rootElement = document.createElement("DIV");
document.body.appendChild(rootElement);
ReactDOM.render(<App />, rootElement);

Same result using the render and alwaysRender props:

...
      <NoMatch render={ match => (match ? null : <NotFound />) } alwaysRender={ true }>
...

Notes

  • NoMatch considers child components without a path (or from) prop as non-matching;
  • The fallback component is always rendered before children.