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 🙏

© 2025 – Pkg Stats / Ryan Hefner

spec-check

v7.0.0

Published

Executable specification in Markdown for Javascript

Readme

spec-check

Specification check for specifications written in Markdown for Node.js libraries.

Why write a specification, then regurgitate it back into a test? spec-check allows one to write executable specification. Author the specificiation in Markdown with ```js or ```javascript code blocks and spec-check will execute the code blocks against an implementations to ensure it works as intended.

left-pad example

Let's say we implement leftPad in index.js and write specification.md as

## `leftPad(string, length, pad = ' ')`
**when string is shorter than length, add pad on left until string reaches length**
```js
> leftPad('foo', 5)
"  foo"
```

**when string is longer or equal to length, do nothing**
```js
> leftPad('foobar', 6)
"foobar"
```

**when optional pad is provided, use it instead of space**
```js
> leftPad(1, 2, '0')
"01"
```

**when pad is not a string, it will be converted to a string**
```js
> leftPad(17, 5, 0)
"00017"
```

We can check index.js against specification.md using spec-check leftPad=index.js specification.md.

spec-check will load index.js as the variable leftPad for the scope of the test. spec-check then executes all the ```js code blocks. Think of each code block as the Node.js CLI, each > is input that is eval and the output is on the next line. spec-check executes the > lines and checks the output matches expected output in the document.

Usage

Edit package.json scripts.test to be spec-check foo=index.js README.md