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

lavascript

v0.6.5

Published

Literate JavaScript

Readme

LavaScript is Literate JavaScript.

As a programmer who works remotely, two skills are more important than others: written communication and programming itself. I exercise the later far more than the former. And because of that, my love for all things Knuth, and a raging jealousy of Literate CoffeeScript, I wrote LavaScript. LavaScript is Literate Programming for JavaScript.

What is Literate Programming?

A pretty good and concise description of Literate Programming is from this blog describing Literate CoffeeScript which (as stated in the above paragraph) was the predominant inspriation for LavaScript.

A so-called literate program is a program that contains both an explanation of the logic in plain English interspersed with snippets of code that the machine can actually run.

Literate Programming inverts the relationship between comments and code.

Examples

Literate Programming

  • https://github.com/jashkenas/coffeescript/blob/master/src/sourcemap.litcoffee
  • https://gitlab.com/randomenduser/dotfiles/blob/master/.emacs.d/emacs.org
  • https://gist.github.com/jashkenas/3fc3c1a8b1009c00d9df

Literate JavaScript

  • https://github.com/mjstahl/lavascript-loader/blob/master/loader.js.md
  • https://github.com/mjstahl/lavascript/blob/master/bin.js.md
  • https://github.com/mjstahl/lavascript/blob/master/extract.js.md

Advantages

In the Wikipedia article on Literate Programming, Donald Knuth describes its advantages as (emphasis is mine):

... provides higher-quality programs, since it forces programmers to explicitly state the thoughts behind the program, making poorly thought-out design decisions more obvious.

The resulting documentation allows the author to restart his own thought processes at any later time, and allows other programmers to understand the construction of the program more easily.

How the above differs from conventional comments is so important, I thought it should be isolated from rest of the paragraph for emphasis.

This differs from traditional documentation, in which a programmer is presented with source code that follows a compiler-imposed order, and must decipher the thought process behind the program from the code and its associated comments.

The above is not as bad as it used to be but I think the key take away is: we still write to satisfy the machine first, even though many of us agree that source code is read 10x more than it is written.

Installation

# install locally for your project
$ npm install --save-dev lavascript
# install globally to execute on .js.md files anywhere
$ npm install -g lavascript

Usage

$ lavascript [input file or dir] [output dir]

Once installed, you should have access to the lavascript command, which can execute scripts and compile .js.md files into JavaScript files of the same name.

Ecosystem