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

react-switch-render

v0.1.2

Published

react switch render

Readme

react-switch-render

Configure a switch and render content based upon props passed in

Installation

yarn add react-switch-render

OR

npm i react-switch-render

If your not using yarn

Basic Usage

SameplePageFooter.jsx

import React from 'react';
import {createSwitchItem} from 'react-switch-render';

const sameplePageFooter = (props) => {
  const {siteName} = props;
  return (
    <p>I am a unique butterfly on the url: {siteName}</p>
  );
};

export default createSwitchItem('/sample-page')(sameplePageFooter);

Footer.jsx

import React from 'react';
import moment from 'moment';
import {createSwitch} from 'react-switch-render';
import SamplePageFooter from './sameplePageFooter';

const defaultFooter = (props) => {
  return (
    <p>Copyright {props.siteName} {moment().format('YYYY')}</p>
  );
};

// const footerSwitch = createPathnameSwitch(defaultFooter, [SamplePageFooter]);
const footerSwitch = createSwitch(defaultFooter, [SamplePageFooter]);

export const Footer = props => {
  const {pathname, ...args} = props; // App passes in pathname: '/some-route' and args are whatever else you passed down
  return (                           // I am using pathname as the way to switch on which component to render
    <footer className="content-info" role="contentinfo">
      {
        footerSwitch((item) => pathname === item)(args)
      }
    </footer>
  );
};

Alternativly you could use the helper switch which deals with direct routes and deals automatically with pitfalls as such as trailing slashes via this setup:

Footer.jsx v2

import React from 'react';
import moment from 'moment';
import {createPathnameSwitch} from 'react-switch-render';
import SamplePageFooter from './sameplePageFooter';

const defaultFooter = (props) => {
  return (
    <p>Copyright {props.siteName} {moment().format('YYYY')}</p>
  );
};

const footerSwitch = createPathnameSwitch(defaultFooter, [SamplePageFooter]);

export const Footer = props => {
  const {pathname, ...args} = props;
  return (
    <footer className="content-info" role="contentinfo">
      {
        footerSwitch(pathname, args)
      }
    </footer>
  );
};

About

This project was born out of the need for a need for a re-usable scalable solution to change what apears in the footer depending on the route. Allot needs to be done as such as remove react as a dependanciy as this actually doesn't need react (maybe it should be renamed too :|) but it does what it needs to