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-reexport

v2.1.0

Published

Allows re-exporting a node module

Downloads

15

Readme

babel-plugin-reexport

Allows re-exporting a node module

Usage

CLI

npx babel ./node_modules/some-package/dir --out-dir ./export-dir --plugins=reexport

Programatically

Typically this is what you'd need to do to make sure that the path of the package you're trying to export is resolved by node.

/* eslint-disable no-console */

const path = require('path');
const { spawn } = require('child_process');

const pkgPath = path.dirname(require.resolve('some-package/dir'));
const babelPath = require.resolve('@babel/cli/bin/babel');
const configPath = path.join(__dirname, '.babelrc');
const outPath = path.join(process.cwd(), 'export-dir');

const babel = spawn(
  babelPath,
  [pkgPath, '--out-dir', outPath, '--config-file', configPath],
  {
    stdio: [process.stdin, process.stdout, process.stderr],
  }
);

Output

The generated output files would contain only the re-export statements from the original package.

For example this

// some-package/dir/MyClass.js

class MyClass {}

export default MyClass

outputs this

export { default } from 'some-package/dir/MyClass'

This plugin supports the following

  • Default exports: export default MyClass -> export { default } from "<path>"

  • Named default exports: export { default } from './MyClass' -> export { default } from "<path>"

  • Named exports: export const Foo = 'bar' -> export * from "<path>"