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

rollup-plugin-es-module-interop

v2.1.0

Published

change the rollup commonjs output for external imports to check `module.__esModule`

Downloads

26

Readme

rollup-plugin-es-module-interop

change the rollup commonjs output for external imports to check module.__esModule

What?

By default, when rollup is configured to output format: 'cjs' code, its require calls look like this:

function _interopDefault (ex) { return (ex && (typeof ex === 'object') && 'default' in ex) ? ex['default'] : ex; }

var external = _interopDefault(require('external'));

That is, if the imported CommonJS module has a .default property, external will be equal to require('external').default. Else, it will be equal to require('external').

This makes ES modules that were compiled to CommonJS and then published to npm work transparently, because they put their default exports on a .default property. But some CommonJS modules also use the .default property as an actual exported value, and not as a "default export". joi is one example.

Babel uses a different check than Rollup does; it checks for the __esModule property, and if it exists, uses require('external').default. Else, it will use require('external'). The __esModule property is added by every compiler that I know of, and CommonJS modules that have a .default property will not be falsely detected as compiled ES modules.

This plugin swaps the Rollup version of _interopDefault for Babel's version. So, with this plugin you can import joi from 'joi' and it'll work!

npm travis standard

Install

npm install rollup-plugin-es-module-interop

Usage

// rollup.config.js
import esModuleInterop from 'rollup-plugin-es-module-interop'

export default {
  plugins: [
    esModuleInterop()
  ]
}

There are no options. rollup-plugin-es-module-interop will replace the _interopDefault implementation in all format: 'cjs' outputs.

License

Apache-2.0