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

esm-to-plain-js

v1.2.5

Published

Simplistic string substitution to replace export with a globalThis assignment (CLI tool designed for use in npm package.json scripts)

Readme

esm-to-plain-js

Simplistic string substitution to replace export with a globalThis assignment (CLI tool designed for use in npm package.json scripts)

License:MIT npm Build

esm-to-plain-js transforms an ES modules file into a plain JavaScript file for browsers by commenting out the imports and replacing the export statement wth globalThis assignments.  The command's console output includes a timestamp and formatting helpful in build systems.

A) Setup

Install package for node:

$ npm install --save-dev esm-to-plain-js

B) Usage

1. Synopsis

esm-to-plain-js [SOURCE] [TARGET]

Parameters:

  • The first parameter is the source file.
  • The second parameter is the target file or folder (use the --folder flag).

2. npm package.json scripts

Run esm-to-plain-js from the "scripts" section of your package.json file.

Example package.json script:

   "scripts": {
      "make-plain-js": "esm-to-plain-js --cd=build web-app.esm.js web-app.js"
   },

3. Command-line npx

Example terminal commands:

$ npm install --save-dev esm-to-plain-js
$ npx esm-to-plain-js web-app.esm.js web-app.js

You can also install esm-to-plain-js globally (--global) and then run it anywhere directly from the terminal.

4. CLI flags

Command-line flags: | Flag | Description | Values | | --------- | ---------------------------------------------- | ---------- | | --cd | Change working directory before starting copy. | string | | --note | Place to add a comment only for humans. | string | | --quiet | Suppress informational messages. | N/A |

5. Examples

  • esm-to-plain-js --cd=build web-app.esm.js web-app.js Transforms build/web-app.esm.js to build/web-app.js

  • esm-to-plain-js web-app.esm.js web-app.js --quiet Displays no output.

C) Application Code

Even though esm-to-plain-js is primarily intended for build scripts, the package can be used programmatically in ESM and TypeScript projects.

Example:

import { esmToPlainJs } from 'esm-to-plain-js';

const result =
   esmToPlainJs.transform('build/web-app.esm.js', 'build/web-app.js');

console.info('Execution time:', result.duration, 'ms');

See the TypeScript Declarations at the top of esm-to-plain-js.ts for documentation.


MIT License

See the runScriptsConfig section of package.json for a clean way to organize build tasks:

  • 🎋 add-dist-header —  Prepend a one-line banner comment (with license notice) to distribution files
  • 📄 copy-file-util —  Copy or rename a file with optional package version number
  • 📂 copy-folder-util —  Recursively copy files from one folder to another folder
  • 🪺 recursive-exec —  Run a command on each file in a folder and its subfolders
  • 🔍 replacer-util —  Find and replace strings or template outputs in text files
  • 🔢 rev-web-assets —  Revision web asset filenames with cache busting content hash fingerprints
  • 🚆 run-scripts-util —  Organize npm package.json scripts into groups of easy-to-manage commands
  • 🚦 w3c-html-validator —  Check the markup validity of HTML files using the W3C validator