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

selfexplanatory

v0.0.1

Published

Make your functions and methods self-explanatory with this simple wrapper

Downloads

3

Readme

selfexplanatory.js

Make your functions and methods self-explanatory with this simple wrapper.

Bring documentation right where it's needed

Whatever you're creating, a library or an API or a widget - if you want someone to use it, let them do so without even looking for the documentation. You know they prefer it that way.

Works in the browser and in nodejs. (npm install selfexplanatory)

What it does

Whenever someone sees the explained function in developer tools, on an object listing etc. it will show the instructions instead of bits of its definition.

If the function gets called incorrectly, It will throw an error containing complete usage information. No need to browse documentation anymore!

Let's explain how it works

explain( <object:explanation>, <function: yourmethod> )
    // returns: function with some special behaviour

A more complete example maybe:

myMethod : explain({
    args: "<string: url>,<function: success callback>",
    description: "does stuff",
    returns: "string: result",
    validator: function (url) {
        return (typeof url === "string");
    }
}, function (url, callback) { ... });

The explanation object consists of the following:

  • args required a single line describing arguments of the function
  • description required any description of the function you want to give
  • returns optional just say what gets returned
  • validator optional a function that will get called before the actual explained method with the same arguments. If the function returns something falsy, an error is thrown with the whole explanation in it. If validator returns truthy, your method gets called.

explained method will correctly resolve this reference.

When an invalid call is made, this is thrown:

Usage: function( <string: url>,<function: success callback> )
does stuff 
returns: string: result

I don't recommend explaining constructor functions and prototypes, because you loose the instanceof feature.