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

witness

v0.0.2

Published

Witness (n) 3. One who hears; a listener.

Downloads

3

Readme

witness

Witness v. 3. to bear witness to; testify to; give or afford evidence of.

Overview

The witness is an intelligent file content cache that keeps track ( optionally on a per-caller basis) of the state of a file.

Installing

Witness may be installed using Node and npm.

npm install witness

Usage

Witness can be used on a individual persistent basis or as a listener.

// For this example assume we have three files layed out as follows:
//  - src/one.coffee
//  - src/two.coffee
//  - src/three.coffee

// Require the witness and initialize it.

Witness = require('witness');
audtior = new Witness(/* The persistent cache file can be passed in here;
                         defaults to './.witness-cache' */);

// Checking the state of some files.

witness.state('src/one.coffee');   // == 'added'
witness.state('src/two.coffee');   // == 'added'
witness.state('src/three.coffee'); // == 'added'
witness.state('src/one.coffee');   // == 'ready'

// Now assume we have modified the content of one of 'src/one.coffee'.

witness.state('src/one.coffee');   // == 'changed'
witness.state('src/one.coffee');   // == 'ready'

// To allow a single process to maintain its event queue independent of another
// in a persistent way, one may specify a context as the second argument
// to `witness::state`.

witness.state('src/one.coffee', 'apple');   // == 'added'
witness.state('src/one.coffee', 'apple');   // == 'ready'
witness.state('src/one.coffee', 'orange');  // == 'added'
witness.state('src/one.coffee', 'orange');  // == 'ready'

// Now if we assume we modified the content again. Notice how 'apple' and
// 'orange' only get notified about the changed event once.

witness.state('src/one.coffee', 'apple');   // == 'changed'
witness.state('src/one.coffee', 'orange');  // == 'changed'
witness.state('src/one.coffee', 'apple');   // == 'ready'
witness.state('src/one.coffee', 'orange');  // == 'ready'

// This is to be used at the end of process; this writes the in-memory
// cache to a persistent file.

witness.store();

License

Unless otherwise noted, all files contained within this project are liensed under the MIT opensource license. See the included file LICENSE or visit opensource.org for more information.