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

@reactioncommerce/babel-remove-es-create-require

v1.0.0

Published

A Babel plugin that removes `createRequire` calls

Downloads

15,829

Readme

@reactioncommerce/babel-remove-es-create-require

A Babel plugin.

If you create a Node 12 project with ECMAScript (ES) modules enabled, you will likely be doing this in a few places to import from CommonJS modules:

import { createRequire } from "module";

const require = createRequire(import.meta.url);

This is the official way to get the require function in a module file.

Now let's say you want to add some Jest tests. Unfortunately Jest does not yet natively parse ES modules, and it doesn't like import.meta, so you'll need Babel configured for tests only.

Install @babel/core, babel-jest, @babel/preset-env, and two plugins that take care of transforming your ES modules:

npm i --save-dev @babel/core @babel/preset-env babel-jest babel-plugin-transform-import-meta babel-plugin-transform-es2015-modules-commonjs

The babel-plugin-transform-es2015-modules-commonjs plugin does most of the transformation to CommonJS and babel-plugin-transform-import-meta transforms the import.meta code into something Jest will accept. But there's still a problem...

const require = createRequire(import.meta.url);

Those pesky createRequire calls are still in there, and now they're causing confusion. We no longer need them because require will now work automatically based on the file being CommonJS.

This is where this package comes in. It does only one thing: removes all lines where you're calling createRequire. Install it the same way you installed the other Babel plugins:

npm i --save-dev @reactioncommerce/babel-remove-es-create-require

Then add it to your Babel config plugins list. Here's an example babel.config.js file that should work for a Node 12 project with ES modules enabled.

module.exports = function (api) {
  api.cache(false);

  return {
    presets: [
      [
        "@babel/preset-env",
        {
          targets: {
            node: "12"
          }
        }
      ]
    ],
    plugins: [
      "babel-plugin-transform-import-meta",
      "module:@reactioncommerce/babel-remove-es-create-require",
      "transform-es2015-modules-commonjs"
    ]
  };
};