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

require-or-import

v0.1.1

Published

Dynamically `require` CommonJS or `import` ECMAScript modules with consistent behavior.

Downloads

498

Readme

Require or Import

Dynamically require CommonJS or import ECMAScript modules with consistent behavior.

Why?

Node officially supports both CommonJS (CJS) and ECMAScript modules (ESM)! Unfortunately, there inherent inconsistencies between the two formats, which can become difficult when loading a file of an unknown format.

This package attempts to smooth over those inconsistencies.

What does it do?

For authors of packages using native ECMAScript modules requireOrImport does not introduce any new behavior. It wraps import as a convenience.

For authors of packages using CommonJS modules requireOrImport uses either require or import according to Node's interoperability semantics. requireOrImport loads CommonJS modules as if they were loaded using import in an ECMAScript module environment.

Specifically, requireOrImport is an asynchronous function which always loads CommonJS modules as a namespace with a default export key pointing to the CommonJS module.exports value, as defined by Node's CommonJS Namespace behavior. Named exports are exposed using cjs-module-lexer.

Who should use this?

requireOrImport may be useful if you

  • distribute both CommonJS and ECMAScript module entry points in your package
  • distribute a compiled version of your sourcecode (although Node allows it, compilers tend to disallow mixed usage of require and import)
  • need to load a file of an unknown format (like a user-supplied configuration file) and need that object to adhere to a consistent interface

Example

When loaded with requireOrImport(), the following files all return Promise<{ default: { test: 'abc' } }>.

// test.cjs
module.exports = { test: 'abc' };
// test.mjs
export default { test: 'abc' };
// test.js below `package.json` with `"type": "commonjs"`
module.exports = { test: 'abc' };
// test.js below `package.json` with `"type": "module"`
export default { test: 'abc' };

When loaded with requireOrImport(), the following files all return Promise<{ test: 'abc' }>.

// test.cjs
exports.test = 'abc';
// test.mjs
export const test = 'abc';
// test.js below `package.json` with `"type": "commonjs"`
exports.test: 'abc';
// test.js below `package.json` with `"type": "module"`
export const test = 'abc';