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

better-history-api

v1.0.1

Published

A better way to interact with the browser history API

Readme

I needed to interact with the browser's History object, but it was too mind-bending. So I made this abstraction and then I was able to get my job done.

These functions update and return state using a single property on the real state object, minimizing your odds of bashing history state set by some other part of your app when you use this API.

API

const historyState = require('better-history-api')

historyState.update(newState)

Updates the existing state for the current history item.

The new state object you pass in is merged with the existing state with Object.assign.

state = historyState.get()

Returns the state object for the current history item.

historyState.addBeforePushStateMiddleware(fn)

This adds a callback/middlewarey function that will be called before pushState is called, no matter who is calling pushState.

Your function will be passed the current (pre-pushState) state, and will give you a chance to change it before the history stack changes.

historyState.addBeforePushStateMiddleware(
	state => Object.assign(state, { position: currentScrollPosition() })
)

Events

The historyState object is an event emitter that emits these events:

new state

Emitted immediately after pushState is called, while the state object is fresh and shiny.

old state

Emitted whenever a popstate event happens with any associated state. Emits the state object.

License

WTFPL