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

madwizard

v9.0.7

Published

Turn Markdown into Wizards

Downloads

1,359

Readme

Node.js CI npm version

Automatic Wizards, from Markdown

Live madwizard

READMEs are a great way disseminate broad knowledge, but can often be a frustrating way to accomplish a specific task. Documentation is prone to rot. Screenshots and command lines invariably go out of date. Sometimes a README may never have worked as written, due to gaps in the documented tasks, divergences from the implementation, or incompletely specified prerequisites.

Even for complete and up-to-date READMEs, it is often unclear how to turn the documentation into a reliable plan of execution. Which code blocks are optional? Which have I already done on my laptop? How about in my cluster? How much of the overly general documentation is relevant to my system?

madwizard automates testing and consumption of documentation. Point madwizard at markdown, and it can generate an execution plan, and help you (and your users) execute these reliably.

The madwizard User Experience

With madwizard, several interaction modes are possible.

  • Task Graph Library: point to your markdown documentation and madwizard generates an execution plan.

  • Test Rig: you may use madwizard to run through that plan in an automated fashion.

  • ASCII CLI Wizards: a madwizard plan allows for choice, and includes an executor that interrogates the user using a familiar terminal Q&A experience, enlisting their help in guiding the plan.

  • Graphical Wizards: the wizard executor supports inversion of control, whereby a Q&A exchange may be intercepted and presented with a custom, e.g. graphical, interface.

Installation

npm install madwizard        # consume as a library
npm install -g madwizard-cli # consume as a CLI tool

The CLI package includes a copy of the guidebook store. If you want to roll your own collection of guidebooks, you can install madwizard-cli-core, which is the same, but without a copy of the guidebook store.

Kicking the Tires

After installing madwizard-cli, you can try some of the demo guidebooks:

madwizard demo/hello
madwizard demo/choice
madwizard kubernetes/choose/ns

Next Steps