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 🙏

© 2026 – Pkg Stats / Ryan Hefner

history-event

v0.0.3

Published

history is an interface for the pushstate and replacestate event.

Readme

English | 简体中文

HistoryEvent is an interface for the pushstate and replacestate event.

A pushstate and replacestate event is dispatched to the window every time, if the history entry being activated was created by a call to history.pushState() or was affected by a call to history.replaceState().

Why

It is well known that browsers already provide a popstate event. However, the popstate event is only triggered by certain browser actions, such as clicking the back button (or calling history.back() or history.forward() in JavaScript). That is, navigating between two history entries in the same document will trigger this event. Calling history.pushState() or history.replaceState() will not trigger the popstate event.

In some cases, we need to know that the browser has newly opened or replaced a route and do some additional processing before switching, such as:

  1. blocking the routing switch.
  2. doing buried reporting when a route switch occurs.
  3. setting additional history states.

Install

npm install history-event
# yarn add history-event
# pnpm add history-event

Usage

HistoryEvent is more like a polyfill and must be injected on the first line of code in the program.

// polyfill.js
import historyEventPolyfill from "history-event";
historyEventPolyfill();

// main.js
import "./polyfill";
// import 'others';
// ...

// case.js
window.addEventListener("pushstate", function (event) {
  event.preventDefault(); // blocking the opening new route
});
window.addEventListener("replacestate", function (event) {
  event.preventDefault(); // blocking the replacing current route
});

In addition to providing pushstate and replace events, the HistoryEvent stores information about the next navigation on the state property of each event (accessed via event.state.navigation).

Each navigation stores a key and index, with the key representing the route's unique navigation identifier and the index representing the index position (starting at 0) in the current route's sub-history stack.

window.addEventListener("pushstate", function (event) {
  console.log(event.state.navigation.key); // unique key of new navigation
  console.log(event.state.navigation.index); // history index of new navigation
});
window.addEventListener("replacestate", function (event) {
  console.log(event.state.navigation.key); // unique key of replacing navigation
  console.log(event.state.navigation.index); // history index of replacing navigation
});
document.querySelector("#submit").addEventListener("click", function () {
  // go to home page after submit
  history.go(-history.state.navigation.index);
});