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 🙏

© 2025 – Pkg Stats / Ryan Hefner

gulp-packager

v2.0.1-a

Published

Gulp build plugin based on neobuilder

Downloads

33

Readme

Gulp-packager

The simplest vanilla ts/js packager supporting base import/export operation.

  • Suitable for vanilla js/ts project or for beginners

  • Includes a customized gulpfile.js with a typescript observer for quick start.

Installation

npm install Sanshain/gulp-packager

or

npm i gulp-packager

Examples

For descriptive reasons the examples below assumes the following task in gulpfile.js:

gulp.task('build', function() {

    let src = './samples/**/init.ts';
    
    return gulp.src(src)                       
        .pipe(cache(src))
        .pipe(rename((path) => path.extname = '.js'))                              
        .pipe(packager({ release : true })) 
        // .pipe(ts())
        .pipe(gulp.dest('./samples'))
});

Example 1

__common.ts file:

let r = 7
function asd(){}

export let months = ['Jan', 'Feb', 'Mar', 'Apr', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'];
export var a = 6;
export function Ads(arg){}
export class Asde{}

and init.ts:

import * as com from "./__common"

var a = com.a;
var c = 7540;

turn out the content inside init.js in the same directory:

//@modules:


const $$__commonExports = (function (exports) {
 let r = 7
	function asd() { }
	
	let months = ['Jan', 'Feb', 'Mar', 'Apr', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'];
	var a = 6;
	function Ads(arg) { }
	class Asde { }
	
	exports = { months, a, Ads, Asde };
	
	return exports 
})({})


//@init.ts: 
const com = $$__commonExports;

var a = com.a;
var c = 7540;
{

    let r = 7
    function asd(){}

    let months = ['Jan', 'Feb', 'Mar', 'Apr', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'];
    var a = 6;
    function Ads(arg){}
    class Asde{}

    var com = {
     		months:months,
    		a:a,
    		Ads:Ads,
    		Asde:Asde 
    }
}

var a = com.a;

var c = 7540;

Example 2

init.ts contains:

import {months, Ads} from "./__common"

var a = months;

var c = 754;

output:

let months = ['Jan', 'Feb', 'Mar', 'Apr', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'];

function Ads(arg){

}

var a = months;

var c = 754;

Attention

Recommends to use import {name} from "./filename" statement just for independent of any global variables classes and clear functions in imported file.

despite the fact that the standard allows such actions, the use of global variables in object-oriented programming is considered a bad practice among developers. This is why we did not include support for this feature.

If you have many global constants or variables in the imported file, please use import * as name from './filename' statement instead.

I should also note that this plugin does not currently support importing npm packages. If your needs are beyond the scope of this package, I suggest using rollup.

options:

  • release : true - disable all comments inside importing file

Advanced features:

Besides using import * as name from './...', import {name} from './...' you can also use `import './...``. But this option does not intended for types/class imports - what will you get a hint about in this case

Other featres:

If you need to skip some import statements, you should to wrap it into following comment with lazy keyword:

/*-lazy*/
import * as lazy from "./__common"
/*lazy-*/

In this case the multiple comments with lazy word in output file will be removed including all import content between them