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

vocalize

v0.0.1

Published

# `vocalize` a framework for pure-data web applications, for Node.js and Chrome

Readme

Please note that this project and readme are currently an active work in progress.

vocalize

a framework for pure-data web applications, for Node.js and Chrome

Copyright © 2017 Alex Yuly

Motivation

Many software applications deal with manipulating and delivering information to human or machine users, but most of these applications model data indirectly, in terms of instructions interpreted by computer processors. This makes application development needlessly inefficient, because these coded models can only produce useful information at runtime, which obfuscates it during development. Many different algorithms can be used to model a given set of data over time, so application developers tend to repeatedly solve the same problems in various suboptimal ways.

If modeling data flow and user experience is more important than modeling CPU execution and memory allocation, then an application should entirely encapsulate all imperative processing within a higher level of abstraction. In such a data-driven model, fundamental units of execution would be encapsulated within strongly typed operations and combined into reusable components. Each component would be solely responsible for how it processes incoming data, and for what and when it delivers data to a constant set of other components. This stands in stark contrast to many so-called "object-oriented" systems (which are nothing more than collections of subroutines loosely grouped by topic), in which any object may be responsible for managing the behavior of any other objects. In such a system, data and control are tightly coupled, but in an pure-data system like vocalize, every expression is data including the relationships amongst data, and control is an abstract convention built into the framework.

Specification

The VOCAL Design Principle

Values |> Operations |> Components |> AppLication

...or in JavaScript: Application(Components(Operations(Values)))

VOCAL is an acronym for a design principle that enforces a hierarchy of responsibility within an application, expressed through forward function application:

  • Values: sources and sinks of strongly typed data
  • Operations: normalized units of execution that map n sources to a sink
  • Components: directed graphs of connected operations that map n sources to a sink
  • Application: a component with a runnable source
  • L... live long and prosper 🖖

One way to think of VOCAL is components talking to other components to which they have a relationship. It is a realization of complete, pure object-oriented encapsulation in the truest sense. It is the application of functional reactive programming to the brilliant ideas that underpin Smalltalk, with absolutely zero imperative syntax.

Usage of JSON

JSON (JavaScript Object Notation) is the defacto data markup language of the Web. The vocalize runtime engine, built on Node.js, adopts it out of convenience and utility. JSON offers a fine balance between simplicity and expressive power, and it interfaces seamlessly with JavaScript. Each unit of "code" in vocalize is a type definition in .word format (a subset of JSON specific to vocalize). Each type definition defines relationships to other type defintions, which defines a directed graph that models the behavior of the type.

Static Type System

All type names are notated as strings, which may contain spaces or any other valid JSON characters. Conventionally, all type names should be notated in lower case with spaces added for names with multiple words. A type in vocalize is like a common noun in English.

Value Types

A value type is notated with the name of the type and nothing more.

  • number type: notated as "number"
  • string type: notated as "string"
  • boolean type: notated as "boolean"

Generic Types

A generic type is a type which is a function of one or more other types. It is notated as an object with a single key which is the name of the type, and whose value is 1 or more type arguments. There are two basic generic types, vectors and structs.

vector

A vector is a type of data backed by a JSON array. Unlike an array, its values are all of a single type Type, notated like this:

{
    "vector": Type
}

struct

A struct is a type of data backed by a JSON object. Unlike an object, a single combination of keys and types forms a single type of struct, notated like this:

{
    "struct": {
        "Key A": A,
        "Key B": B,
        "Key C": C,
        ...
    }
}

Type Templates, Type Application, and null Type

Type Aliases

An instance of a generic type may be aliased by defining a .word file notated like this:

{
    "alias": "my struct",
    "of": {
        "struct": {
            "Name": "string",
            "Phone": "number",
            "Emails": {
                "vector": "string"
            }
        }
    }
}

A type alias may be generic:

{
    "alias": "my templated matrix",
    "template": {
        "Type": null
    },
    "of": {
        "vector": {
            "vector": "Type"
        }
    }
}

Operation Types

An operation is a flavor of generic type which is backed by a fundamental unit of execution. A FUE (pronounced "fuey") is a JavaScript module which implements a normalized unit of behavior that is beyond the scope of vocalize itself, such as core arithmetic like addition and multiplication, a native feature of Node.js or Chrome, or some external library.

Sources

The Sink

Abstract Operations

Component Types

Application Types