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

@mwm/describe

v2.5.0

Published

Describe is a thin wrapper around Tap that automates common conventions for testing software.

Downloads

3

Readme

@mwm/describe

This is preview release, and doesn't currently do public/private exports.

Describe is a thin wrapper around Tap that automates many of the common conventions I use when testing software. Specifically:

  1. Each module has a dedicated subfolder.
  2. The module's source and tests live in that same folder.
  3. Public exports are made by the module's index.js file.
  4. Exports from any other file are private to that module and should never be imported by sibling or parent modules.

For example:

  • ../module/module.js may import from ./helper.js, but may not import from ../sibling/helper.js.
  • ../module/module.js may import from ../sibling/index.js.