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 🙏

© 2026 – Pkg Stats / Ryan Hefner

modulestrap

v0.11.6

Published

A basic JS module bootstrap

Readme

modulestrap

Social Media Photo by Danielle MacInnes on Unsplash

A basic JS module bootstrap: npx modulestrap project-name


The goal of this binary module is to bootstrap any JS module that would like to land on browsers, as well as NodeJS.

modulestrap project-name
  --babel      # to transpile for older browsers
  --cover      # to include coverage tools
  --node       # to create a NodeJS only module
  --ungap      # to include polyfills
  --force      # to overwrite existent projects
  --ucjs       # use ucjs instead of ascjs
  --no-default # to avoid exporting module.default
  --no-interop # alias for --no-default

Accordingly with the passed flags, the binary will create project-name and initialize it with most common tools to create dual modules.

Example / How to

npx modulestrap my-project --babel
cd my-project
code .
# write your module in ./esm/ folder
# the `index.js` is already there
# once you've done
npm run build

Above procedure will create all files for both CommonJS and ESM module + it will transpile to index.js and minify to min.js for browsers.

It is suggested to write a test too, either via --cover flag, or manually.

At that point, you can publish to npm your module.