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

patch-history

v1.0.0

Published

A history module for patchcore compatable apps.

Downloads

10

Readme

Patch-history

Manage your history state in patchcore based apps. Patchcore and related modules use depject to provide (give) and consume (need) dependencies.

API

history.obs.store

(Not generally for public use)

The history store in the form of a Mutant Array. This is an observeable, which is excellent for building things with Mutant.

history.obs.location

The current location as in history, as Mutant Value.

A crude was to access the contents of a Mutant observeable is to call it:

const currentLocation = api.history.obs.location() // observeable
currentLocation() // => array

You can also subscribe listeners which will be called when the observeable updates:

const listener = (location) => console.log('new location', location)
currentLocation(listener)

history.sync.push

A synchronous method which allows you to push a new location onto the end of the history.

history.sync.back

A synchronous method which moves the current location back a step in histroy.

Example

// main.js
const combine = require('depject')
const entry = require('depject/entry')
const nest = require('depnest')

const sockets = combine(
  require('./index.js'), // an object of depject modules
  require('patch-history'),
  require('patchcore')
)

const api = entry(sockets, nest('app.html.app', 'first'))
const app = api.app.html.app()
// homePage.js
const html = require('yo-yo')

export.gives = nest('app.page.homePage')

exports.needs = nest({
  'history.sync.push': 'first'
  'history.sync.back': 'first'
})

exports.create = (api) => {
  return nest('app.page.homePage', homePage)

  function homePage () {
    const goToSettings = () => api.history.sync.push({ page: '/settings' }) 
    // you can push whatever you want into history, it's just an array

    return html`
      <div>
        Hi, check your <button onclick=${goHome}> settings </button>
      <div>
   `
  }
} 
// app.js
export.gives = nest('app.html.app')

exports.needs = nest({
  'history.obs.location': 'first',
  'history.sync.push': 'first',
  'router.sync.router': 'first'
})

exports.create = (api) => {
  return nest('app.html.app', app)

  function app () {
    const currentLocation = api.history.obs.location()
    currentLocation(renderPage)
    // currentLocation is an observable which can be passed listeners
    // these will be called when the location changes

    api.history.sync.push({ page: '/home' })
  }

  function renderPage (newLocation) {
    const newView = api.route.sync.router(newLocation)

    document.body.appendChild(newView)
    // crude 'rendering'!
  }
}