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

jsmd

v2.0.0

Published

jsmd ensures that you will never have outdated and non-working JavaScript code in your README files.

Downloads

1,323

Readme

NPM version Build Status

jsmd

Synopsis

jsmd ensures that you will never have outdated and non-working code in your README files.

Usage

Usage: jsmd <path>

Options:

  --show      display the compiled JS after execution
  --help      display this help message
  --version   display the version number

How to use it

Just write your README files in GitHub Flavored Markdown as usual. The only thing that you have to add is the actual assertions. So here is a small example that will hopefully illustrate how assertions look:

var fs = require('fs');

fs.unlink('/tmp/this-is-stupid', function(err) {
  typeof err; // => 'object'
});

In this simple example we expect that the type of err is equal to 'object'. As simple as that.

In order to verify if everything works properly just supply the desired file to jsmd and it will verify it for you:

$ jsmd README.md

See the examples for more info.

Which code blocks get evaluated

In order jsmd to recognize your JavaScript code elements, you have to specify them either as "js" or "javascript".

To get JavaScript syntax highlighting, without jsmd running the code, specify the code block as "node".

```node
var rm_rf = require('rimraf')
rm_rf('/usr/bin')
```

Hidden setup

Sometimes you don't want to put helper code into your readme file, but it's necessary in order to perform the tests. In this case, you can simply add special html comments which jsmd will extract and put inside the compiled file.

<!-- js
var server = require('express');
server();
-->

That way, GitHub won't visualize the comment but jsmd will be able to parse it.

How it works

jsmd has very simple flow, that looks like this:

  • First jsmd will parse and extract all JavaScript code elements
  • It will search the code snippets for "assertions". Assertions look like this Math.min(1, 2) // => 1
  • It will compile the JavaScript code with the assertions and it will try to execute it
  • It will report failures if any

Installation

$ npm install jsmd -g

Tests

Running the tests

$ npm test

Test coverage

$ npm run-script coverage

Credits

Special thanks to:

Related projects

  • Doctest.js
  • xplain - JavaScript API documentation generator that uses unit tests as examples

License

(The MIT License)

Copyright (c) 2013 Veselin Todorov [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.