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

diso.core

v0.0.33

Published

Client / Server

Readme

diso.core

0.0.33

Notes

The top level export includes an object with two properties:

var Core = require('diso.core');
var Client = Core.Client;
var Server = Core.Server;

However, this introduces an issue for clientside bundlers such as Browserify, which would try to include Server code in the client bundle, causing failures from serverside-only libs

For this reason the js builds are exported to the top level of the package so that client and server directories can be required independently as follows

var Client = require('diso.core/Client');
var Server = require('diso.core/Server');

Description

Client/Server/Derp

Research

documentation

  • https://github.com/tschaub/grunt-gh-pages

frameworks to check out

  • https://github.com/walmartlabs/lazojs/wiki/Overview
  • http://facebook.github.io/react/docs/flux-todo-list.html
  • http://react-components.com
  • http://lhorie.github.io/mithril/index.html

security

  • http://www.christian-schneider.net/CrossSiteWebSocketHijacking.html

production environments

  • http://docs.strongloop.com/display/SLC/slc+run
  • https://www.phusionpassenger.com/node_weekly

queues to decouple server and workers / message handlers

  • https://github.com/topcloud/socketcluster
  • http://www.bravenewgeek.com/dissecting-message-queues/
  • http://stackoverflow.com/questions/10620976/rabbitmq-amqp-single-queue-multiple-consumers-for-same-message
  • http://www.rabbitmq.com/tutorials/tutorial-one-python.html
  • http://www.squaremobius.net/rabbit.js/#zeromq

derp rest

http://en.wikipedia.org/wiki/Representational_state_transfer http://en.wikipedia.org/wiki/HATEOAS http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm http://en.wikipedia.org/wiki/HTTP https://github.com/prettymuchbryce/node-http-status/blob/master/lib/httpstatus.js http://en.wikipedia.org/wiki/List_of_HTTP_status_codes https://dev.twitter.com/docs/error-codes-responses https://github.com/visionmedia/express/blob/master/examples/route-map/index.js#L47

Todo

  • headers, status from page load -> container
  • styles, scripts
  • metadata updating / between redirects / client page changes
  • PAGE TRANSITIONS
  • PAGE MODALS
  • Introduce queue / messaging intermediary so that socket connections can be scaled across multiple servers. in process, requesthandler / ServerActions need to be replaceable with acceptor pattern that converts http request into "pageRequest" that is pushed onto queue and handled by consumers