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

next-router-event

v1.0.0

Published

<p align="center"> <img src="https://assets.vercel.com/image/upload/v1607554385/repositories/next-js/next-logo.png" height="128"> <h1 align="center">Next-router-event</h1> </p>

Downloads

12

Readme

Introduction

Next-router-event contains the useRouterEvent hook which is basically a tiny abstraction around next router.events. You can use the hook to easily trigger callbacks on a certain type of router event:

  • routeChangeStart
  • routeChangeComplete
  • routeChangeError
  • beforeHistoryChange
  • hashChangeStart
  • hashChangeComplete

It also adds typescript support which gives you a better idea on what args are passed to the callback!

Quick start

Installation

yarn add next-router-event

or

npm i next-router-event

Examples

Example 1: Imagine that we have a modal that needs to close whenever the use navigates to a different page. In example below the isOpen state will be set to false whenever the routeChangeComplete event is triggered.

import { useState } from 'react'
import useRouterEvent from "next-router-event";

const Modal = () => {
    const [isOpen, setIsOpen] = useState(false)

    useRouterEvent('routeChangeComplete', () => setIsOpen(false))

    ...
}

Example 2: The hook can also be handy to trigger certain datalayer updates with regards to google analytics.

import useRouterEvent from "next-router-event";

const handleRouteChange = () => {
  window.dataLayer.push({
    event: "pageview",
    page_location: window.location.href,
  });
};

const usePageView = () => {
  useRouterEvent("routeChangeComplete", handleRouteChange);
};

export default usePageView;

Example 3: If a route load is cancelled (for example, by clicking two links rapidly in succession), we can capture this. By looking at the event type typescript knows what args are given to the callback which we can use to do specific stuff.

import useRouterEvent from "next-router-event";

// wrong
const handleRouteChange1 = (err: string) => {
  if (err.cancelled) {
    console.log(`Route to ${url} was cancelled!`);
  }
};

// correct
const handleRouteChange2 = (err: Error, url: string) => {
  if (err.cancelled) {
    console.log(`Route to ${url} was cancelled!`);
  }
};

const useOnRouterError = () => {
  // typescript will complain
  useRouterEvent("routeChangeError", handleRouteChange1);

  // correct
  useRouterEvent("routeChangeError", handleRouteChange2);
};

export default usePageView;

Motivation

A library for the useRouterEvent hook is probably a little bit redundant but I created it with the idea to try out turborepo. This got me into trying out more things like microbundler for bundling and changesets as the way to manage versioning.

Also special thanks to Lee Robinson who wrote a nice article on this matter

Feel free to copy this setup as a boilerplate for your own ideas!