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

esm2cjs

v1.0.2

Published

Also release ES modules as CommonJS modules.

Readme

esm2cjs

Easily compile ES modules to CommonJS modules with functionally equivalent interfaces.

Given a file like foo.mjs:

export default function foo () {}

Generates a file like foo.js:

'use strict';
module.exports = function foo () {};

If that is your main module, in your package.json, you can do:

{
  "main": "./foo"
}

Then, if Node supports modules and someone requires or imports your package, then foo.mjs will be imported, and if Node doesn't support modules, then foo.js will be imported instead.

What you're doing is shipping a native ES module (W00T the future is NOW) yet still offering a fallback for not-yet-upgraded environments.

Usage

Install it: npm i -D esm2cjs

Run it: npx esm2cjs

Continuously rebuild: npx esm2cjs --watch (shorthand: npx esm2cjs -w)

Call it in your package's prepare task so it always runs right before you publish a release, ensuring that your ".js" files are up-to-date with your ".mjs" files:

{
  "scripts": {
    "prepare": "esm2cjs"
  }
}

You can specify which files will be compiled by adding a .esm2cjs file to your package root. This file contains a newline-delimited list of file globs, e.g. a .esm2cjs file like:

*.mjs
bin/cli.mjs

Would compile this directory:

directory/
├── index.mjs
└── bin/
    └── cli.mjs

Into this:

directory/
├── index.js
├── index.mjs
└── bin/
    ├── cli.js
    └── cli.mjs

Extending

esm2cjs uses Babel 6 under the hood. This means that if you want to use syntax extensions (e.g. TC39 proposals, JSX, etc) in your code, you can do that by adding a .babelrc file to your project.