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

test-snippets

v2.0.2

Published

Flexibly test markdown code examples

Downloads

254

Readme

test-snippets npm version build status coverage status

Flexibly test markdown code examples.

A command to extract and run tagged examples in markdown files, and test them against your NPM package.

Your node package is built locally and installed in a subdirectory (by default tests/snippets).

Installation

npm install test-snippets

Usage

You will need a config file, the default config file location is tests/snippets/config.json. This file specifies how to run the snippets.

Take this config file for example:

{
  "es6": { "command": ["node"], "extension": "js" },
  "js": { "command": ["node"], "extension": "cjs" },
  "ts": { "command": ["tsx"], "extension": "ts" }
}

This allows you to tag snippets with "es6", "js" or "ts" in your markdown. Add an HTML comment directly above a code block, using any tags you wish to run it with (separated by commas):

    <!-- snippet: es6,ts -->
    ```js
    import path from 'path';

    console.log(path.join('hello', 'world'));
    ```

To run the command use:

npx test-snippets

This will look through all .md files in the repository (excluding anything in node_modules folders) then locally install the NPM package and run the snippets with it. By default it will use tests/snippets as the test directory.

You can choose specific files:

npx test-snippets README.md hello.md

Or use glob rules:

npx test-snippets "docs/**/*.md"

You can override the ignored files, as a comma separated list:

npx test-snippets "**/*.md" --ignore="README.md,hello.md"

You can override the config file:

npx test-snippets --config=config.json

You can override the test directory:

npx test-snippets --test-dir=test-dir/

Debugging

Test artifacts will be automatically cleaned up, however, you can disable cleanup of tests with the cleanup option:

npx test-snippets --cleanup=false

This will leave the files and node_modules directories in the test directory. This can be useful when debugging failing tests, you can run the code yourself or even debug the installed node module.

Programmatic usage

Call with a list of files, a config file and a directory

import testSnippets from 'test-snippets';

(async () => {
  await testSnippets(['file.md', 'other.md'], 'config.json', 'test-dir/', true);
})();

With CommonJS / require()

const testSnippets = require('test-snippets');

(async () => {
  await testSnippets(['file.md', 'other.md'], 'config.json', 'test-dir/', true);
})();