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-history-pro

v1.0.1

Published

react-router alternative with extra functionality (blocking, full history control) with HistoryPro

Downloads

2

Readme

react-router-history-pro

This module has the same functionallity of BrowserRouter from react-router-dom.

It extends its functionallity using history-pro module instead of history. It can block routes and has a precise controll of navigation events.

I recommend to see history-pro first

This docs are incomplete. I will complete it. Please give me a ⭐ on GitHub if you can.

import HistoryPro from "history-pro"
import { HistoryProRouter } from "react-router-history-pro"

const historyPro = new HistoryPro()

function App() {
  return (
    <div className="App">
      <HistoryProRouter history={historyPro}>
        <Routes>
          <Route path="/" element={<HOME />} />
          <Route path="/about" element={<About />} />
          <Route path="/contact" element={<Contact />} />
          <Route path="/products">
            <Route index element={<Catalog />} />
            <Route path=":id" element={<Product />} />
            <Route path="/other-nested-page" element={<Page />} />
          </Route>
        </Routes>
      </HistoryProRouter>
    </div>
  )

}

/**
 * Returns the HistoryPro instance used by the router
 * it can be used to: push(), pop(), replace(), block(), listen(), and more!
 */
function useHistory(): HistoryPro

/**
 * Returns last navigation event as NavEvent instance
 */
function useHistoryEvent(): NavEvent

/**
 * Returns history location
 */
function useHistoryLocation(): NavLocation

/**
 * Used to block navigation.
 * It can block ⬅➡ keys and, using options, push and pop actions.
 * It returns a block() function. Then you use block(blocker_callback)
 */
function useBlock(): (blocker: (e: NavEvent, stopBlocking: () => void) => void, options?: BlockOptions) => () => void

/**
 * Used to block navigation.
 * It can block ⬅➡ keys and, using options, push and pop actions.
 * It recives directly the blocker function.
 * By default, it will automatically unblock if pushed a new location. Also if component removed.
 * Ej: making appear a modal, you can useBlocker and if modal dissapear it will automatically stop blocking.
 */
function useBlocker(blocker: (e: NavEvent, stopBlocking: () => void) => void, options?: BlockOptions): void

/**
 * Listen all history events.
 * It can be used to cancel event with event.setCancelled(true)
 */
function useHistoryListener(listener: (e: NavEvent) => void): void

/**
 * It can be used only one time on a route. (Is the same history every time for each location)
 * Stores the state on history
 */
function useHistoryState(initial?: any): any[]

/**
 * Returns router basename
 */