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-page-routes

v1.14.0

Published

Simplify coding your react-router-dom <Routes/> and <NavLinks/> by using attributes in your component.

Downloads

4

Readme

react-page-routes

Simplify coding your react-router-dom <Routes/> and <NavLinks/> by using attributes in your component.

How it works

You provide page components containing title and path attributes, and pass them to the package as an array. The package will map the pages to a React-Router component and handle setup for both react router-routes and react-router links.

Setup

Install

npm install react-page-routes

Install react-router-dom and prepare a context provider in a parent component:

npm install react-router-dom
// index.tsx
import { BrowserRouter } from "react-router-dom";

ReactDOM.createRoot(document.getElementById("root") as HTMLElement).render(
  <BrowserRouter>
    <App />
  </BrowserRouter>
);

1. Create Page Components

Add both path and title attributes to all of your Page Components.

Shop.path = '/shop'
Shop.title = 'Shop Now!'

export default function Shop() {
  return <h1>Shop Now Page</h1>
}

The path will be provided to <Route path={}> in the Pages component and <NavLink to={}> in the NavBar component.

The title will be provided to <NavLink>{title}</Navlink> in the NavBar component

2. Create a directory index of all pages

  1. Create Directory.ts file.
  2. Import the directory function.
  3. Import all of your page components
  4. Invoke the directory function, passing all of your page components as props.
  5. export default the results
// Directory.ts

import { routes } from 'react-page-routes'
import Home from './Pages/Home'
import Shop from './Pages/Shop'

export default routes(
  Home,
  Shop,
  // <- add in any additional Page Components here.
)

3. Use in your App

  1. Import the Directory.ts file from step 2
  2. Use the Navbar for handling <NavLinks/>
  3. Use Pages for handling react-router <Routes/>
// App.tsx
import { Directory } from './Directory'

function App() {
  return (
    <div>
      <Directory.NavBar />
      <Directory.Pages />
    </div>
  )
}

4. Customize with a Mapper Function (Optional)

// App.tsx
import { Directory } from './Directory'

const MyCustomPagesMapper = (E) => (
  <Route element={<E />} path={'path' in E ? String(E.path) : ''} key={String(E.name)} />
)

const MyCustomNavBarMapper = (E) => (
  <NavLink key={E.path.toString()} to={E.path.toString()}>
    {E.title}
  </NavLink>
)

function App() {
  return (
    <div>
      <Directory.NavBar map={MyCustomNavBarMapper} />
      <Directory.Pages map={MyCustomPagesMapper} />
    </div>
  )
}

Done

Thanks for trying out this package. Additional questions/ideas/suggestions/contributions are welcome. Visit the github repository issues page, please select relevant Labels