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

readme-to-test

v0.2.0

Published

A simple README code examples validator.

Downloads

27

Readme

readme-to-test

A simple README code examples validator.

Introduction

The readme-to-test libary allows to easily validate code examples defined in the README file.

It finds all JavaScript blocks of code defined in target project's README file and converts them to unit tests. Tests are run with Mocha and can be easily integrated with the build process (and Git's pre-commit hook).

Installation

npm install readme-to-test --save-dev

Command line

The validation can be triggered by executing the following command in the target project's main directory:

node ./node_modules/readme-to-test/validate.js

The README file is automatically located. The validator creates a temporary directory (.tmp by default) and creates a separate self-contained unit test file for each block of JavaScript code found in the README. Then all the generated tests are run with Mocha. The directory is only deleted after a successful validation.

Integrating with the build

The validate-readme-examples script can supplement the existing tests:

{
  "name": "library",
  "version": "1.0.0",
  "main": "main-script.js",
  "scripts": {
    "validate-readme-examples": "node ./node_modules/readme-to-test/validate.js",
    "test": "mocha unit/tests/ && npm run validate-readme-examples"
  }
}

Examples

With console.log

The following block of code:

import library from 'library';

const result = library.someFunction();

console.log(result);
// prints 'result from some function';

will be converted into a unit test:

import assert from 'assert';
import library from './main-script.js';

it('Converts prints statement following console.log to assertion', () => {

    const result = library.someFunction();

    console.log(result);
    assert.deepEqual(result, 'result from some function');
}

No console output

var library = require('library');
// library.version === '1.0'
var assert = require('assert');

it('Converts equality statement to assertion', () => {
  
    var library = require('library');
    assert.deepEqual(library.version, '1.0');
}

If imports are not used the generated tests are compatible with ES5.

Configuration

The libary uses the following default settings:

--opts-file=test/r2t.opts --temp-dir=.tmp --temp-delete-after=true --temp-clear-before=true

The temporary folder settings can be overriden in test/r2t.opts file.

P.S. Yep, the library validates its own README as well!