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

web-pockets

v0.3.1

Published

Build loosely-coupled web-apps without caring about ordering.

Downloads

16

Readme

web-pockets Build Status

Build loosely-coupled web-apps without caring about ordering.

Table of Contents

  1. The Synopsis below is intended to give a taste of what web-pockets is.
  2. The best place to start learning more is the guide.
  3. There are reference docs for all the built-in values.
  4. For those wondering "why bother?" there is Why web-pockets is better than other frameworks.
  5. Some example code using web-pockets:

Synopsis

Create a handler function named app:

var app = require('./')();

app is also a pocket:

app.value('hits', createHitCounter);

function createHitCounter () {
  return new Promise(function (resolve) {
    // Pretend we did something more interesting here
    var hits = {};
    setTimeout(resolve, 1000, hits);
  });
}

You can also define values that are computed per-request:

app.request.value('acceptsJson', requestAcceptsJSON);
function requestAcceptsJSON (request) {
  return /json/.test(request.headers.accept);
}

Use app.route to get going quickly:

app.route('GET *', function (request, hits, acceptsJSON) {
  var count = hits[request.url] = (hits[request.url] || 0) + 1;
  if (acceptsJSON) {
    return { hits: count, url: request.url };
  }
  var message = request.url + ' has been visited ' + count + 'time';
  if (count !== 1) {
    message += 's';
  }
  return message;
});

API

Handler = Pocket & ((Request, Response) => void) & {
  request: PocketProxy
}

module.exports =: (Pocket?) => Handler

The default export takes an optional "root" pocket and returns a handler function that is also a pocket. The handler function has a property named request that is a deferred proxy for the child pocket implicitly created for each request. What this means is that values that should be computed once for the entire app are defined on the handler using e.g. app.value(name, valOrFunction), and values that should be computed once per-request are defined using app.request.value(name, valOrFunction).

See also: API docs for Pocket

License

MIT