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

gulp-es6-exporter

v0.0.5

Published

A VERY rough gulp task for re-exporting directories of es6 modules

Downloads

1,524

Readme

gulp-es6-exporter

A VERY rough gulp task for re-exporting directories of es6 modules

Do not use for anything live, it was just a prototype to see how easy it was to generate re-exporting files for large projects.

Assuming you do not care and want to try it anyway...

var gulp = require("gulp");
var exporter = require("./index");

gulp.task('default', function() {
    return gulp.src("./test/*.js")
        .pipe(exporter("amaze.js"))
        .pipe(gulp.dest('./test'));
});

This would re-export everything within the test directory, into a file called amaze.js.

You can however provide the option root to provide where it is running from:

exporter("amaze.js", { root: "test" })

// Created amaze.js
export * from './test-1';
export * from './test-2';
//etc

// If we were not to use the root option it would output

// Created amaze.js (without root)
export * from './test/test-1';
export * from './test/test-2';
//etc

This would assume it is re-exporting from within the test folder so it would remove the "./test" prefix and put in "./".

There is also for typescript people the option for module to wrap the re-exports within a new module.

exporter("amaze.ts", { module: "spiffy-module" });

// Created amaze.ts
declare module "spiffy-module"
{
    export * from "./test/test-1";
    export * from "./test/test-2";
    // etc
}

This is the reason I made the module to basically wrap my internal files in an external module without having to litter module syntax throughout each.