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 🙏

© 2025 – Pkg Stats / Ryan Hefner

copy-mjs

v0.1.0

Published

🛠 Copy `.js` files from input directory to `.mjs` files in output directory.

Downloads

14

Readme

copy-mjs

Build tool to copy .js files from input directory to corresponding .mjs files in output directory.

Why?

If we have multiple files in a package and we want all of them to be importable we often suggest to users doing it like this:

import module from "package/lib/module";

This normally has a serious drawback because by doing so we often point people to using files authored in CommonJS format (being the lowest common denominator). This prevents bundlers' optimizations such as tree-shaking & scope hoisting (a.k.a. module concatenation).

If we provide a second build in ESM format we might mention it in the docs and propose importing the same thing with i.e. "package/es/module" for people using module-aware bundlers. This is a mental overhead that can be avoided.

I recommend using "proxy directories" technique described by me in this article as it allows wider set of tools to choose appropriate files automatically. I've also created a package which creates such directories for you - cherry-pick.

If you do not like this technique and you'd still like to improve the situation for your users this package might help you in that.

webpack@4 came with .mjs files support. What does it mean? It means that if your user imports "package/module" webpack will try to load package/module.mjs first, before falling back to loading package/module.js (tools not recognizing .mjs will fall back gracefully to .js). This means that we can just put .js files authored in CJS format side by side with .mjs files authored in ESM.

To provide the best developer experience you should either:

  • publish alternate directory
  • or move temporarily your files to root when publishing.

Doing so can allow people to import i.e. "package/module" instead of "package/lib/module".

CLI Options

copy-mjs

Copy `.js` files from input directory to `.mjs` files in output directory.

Options:
  --help, -h        Show help                                          [boolean]
  --version, -v     Show version number                                [boolean]
  --input-dir, -i                                               [default: "esm"]
  --output-dir, -o                                              [default: "lib"]
  --cwd                                                           [default: "."]

Example usage

copy-mjs --input-dir esm --output-dir lib

JS API

copy-mjs exports a default method which copies .js files from input directory to corresponding .mjs files in output directory. It accepts the same options as CLI command.

const copyMjs = require("copy-mjs");

copyMjs({ inputDir: "esm", outputDir: "lib" }).then(() =>
  console.log("Successfully created .mjs files.")
);