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

whatmd

v0.0.3

Published

Module pattern probing tool

Downloads

6

Readme

whatmd

Module pattern probing tool

Motivation

To figure out which JS module definition standards a module complies with. Could be useful when developing your own Node, Bower, etc. modules or when you're troubleshooting why attempts at including a third-party module keep failing.

This is not meant to be a comprehensive diagnostic tool, but an optimistic helper to give you a high-level overview.

Installation

npm install -g whatmd

Usage

whatmd <JS file>

Pass in a JS file to probe for module definition patters. The currently checked patterns are:

  1. Global exports
  2. CommonJS
  3. AMD

Limitations

  1. AMD probing doesn't include a proper browser window emulation environment and therefore modules relying on browser features may fail to initialize and effect probe results.
  2. AMD probing cannot detect global variables defined through the use of variable assignments without var.
  3. AMD probing cannot handle require() calls within module factories.
  4. No pretty output yet. Just dumps a JS object with a bunch of undocumented properties.