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

frampton-history

v0.1.0

Published

A module for managing browser history with frampton.js

Downloads

4

Readme

Frampton-History

Build Status

A module for managing browser history with framptonjs.

Responding to History Changes

Frampton-history exposes a number of properties for responding to changes to browser history. All the properties exposed by frampton-history are Signals (time-varrying values) that can be monitored.

// The current location.
const location = Frampton.History.location;

// This callback will be run initially with the initial location and then every
// time the browser location changes.
location.value((currentLocation) => {
  console.log('current location: ', currentLocation);
});

// If you are just interested in the current path
const path = Frampton.History.path;

path.value((currentPath) => {
  console.log('current path: ', currentPath);
});

// Also current hash
const hash = Frampton.History.hash;

hash.value((currentHash) => {
  console.log('current hash: ', currentHash);
});

// And current search query
const search = Frampton.History.search;

search.value((currentSearch) => {
  console.log('current search: ', currentSearch);
});

History Depth

There is another Signal for monitoring the depth of the current history stack for your application. Each time a history state is added using pushState or removed by a popstate action this Signal will update with the new history depth.

const depth = Frampton.History.depth;

depth.changes((stackDepth) => {
  console.log('items in history: ' + stackDepth);
});

Manipulating History

When using frampton-history to manage browser history you should use the provided methods for pushState, replaceState and setHash. Using these methods will keep the internal state of frampton-history in sync with the actual state of the browser.

const pushState = Frampton.History.pushState;
const replaceState = Frampton.History.replaceState;
const setHash = Frampton.History.setHash;

pushState({
  path : '/test/path',
  name : 'test path'
});

replaceState({
  path : '/test/path',
  name : 'test path'
});

setHash('test-hash');