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

babel-plugin-cjs-esm-interop

v4.0.2

Published

Transform CJS to ESM and vice versa.

Downloads

6,995

Readme

babel-plugin-cjs-esm-interop

Build Status npm version

Transform the differences between CommonJS code (.js, .cjs) and ECMAScript module code (.mjs), based on the official Node.js documentation.

We suggest writing your code as ESM (.mjs, .ts, .tsx, .js with module type) and compiling down to CJS instead of the reverse. This means using new syntax like import.meta, import(), etc!

// Input: mjs
const self = import.meta.url;
// Output: cjs
const self = __filename;

Installation

yarn add --dev babel-plugin-cjs-esm-interop

Add the plugin to your root babel.config.* file and configure the output format option with either mjs (default) or cjs.

module.exports = {
  plugins: [['babel-plugin-cjs-esm-interop', { format: 'mjs' }]],
};

Requirements

  • Linux, OSX, Windows
  • Node 18.12+

Transforms

The following transforms and error handling are applied.

CJS output

  • export, export default
    • Will throw an error if used.
  • import.meta.url -> __filename (with file:// contextually)
  • path.dirname(import.meta.url) -> __dirname (with file:// contextually)

MJS output

  • require(), require.resolve(), require.extensions, require.cache, exports.<name>, module.exports, process.env.NODE_PATH
    • Will throw an error if used.
  • __filename -> import.meta.url
  • __dirname -> path.dirname(import.meta.url)

How to's

If you want to support ESM code, you'll need to move away from certain features, in which you have a few options.

What to replace require() with?

  • Use import() for JS files. Be aware that this is async and cannot be used in the module scope unless top-level await is supported.
  • Use the fs module for JSON files: JSON.parse(fs.readFileSync(path))
  • Use module.createRequire(), which returns a require-like function you may use. More info.

What to replace require.resolve() with?

  • Use the resolve npm package.
  • Use module.createRequire(), which returns a require-like function with a resolver you may use. More info.