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 🙏

© 2026 – Pkg Stats / Ryan Hefner

gulp-amd-util

v0.2.1

Published

This provides couple utilities for working with Javascript AMD modules and gulp pipes.

Readme

gulp-amd-util

This provides couple utilities for working with Javascript AMD modules and gulp pipes.

With this you can create javascript bundles for AMD modules, if you're using RequireJS, or Dojo, or Babel with transform-es2015-modules-amd plugin, among others.

Quick start

Installing with npm

npm install gulp-amd-util --save-dev

Javascript bundle task example (up to version 0.2.0.rc.0)

var gulp = require("gulp");
var gulp_amd_util = require("gulp-amd-util");

// up to version 0.2.0.rc.0, need to call sort before bundle
// and also moduleRoot must have a trailing slash.
gulp.task("js-bundle", function() {
	return gulp.src("source/**/*.js").pipe(
		gulp_amd_util.sort({
			moduleRoot: "my-app/"
		})
	).pipe(
		gulp_amd_util.bundle({
			moduleRoot: "my-app/",
			keepSource: true,
			outputPath: "my-app.bundle.js"
		})
	).pipe(gulp.dest("dist/");
});

Javascript bundle task example (version 0.2.1 and up)

var gulp = require("gulp");
var gulp_amd_util = require("gulp-amd-util");

// version 0.2.1 and up, no need to call sort before bundle
gulp.task("js-bundle", function() {
	return gulp.src("source/**/*.js").pipe(
		gulp_amd_util.bundle({
			moduleRoot: "my-app",
			keepSource: true,
			outputPath: "my-app.bundle.js"
		})
	).pipe(gulp.dest("dist/");
});

Using babel to transpile ECMAScript2015 code to AMD first

import gulp from "gulp";
import gulp_amd_util from 'gulp-amd-util';
import gulp_babel from "gulp-babel";
import gulp_sourcemaps from "gulp-sourcemaps";

const BABEL_CONFIG = {
    "plugins": [
        "external-helpers",
        "add-module-exports",
        "transform-es2015-modules-amd"
    ],
    "presets": [ "es2015" ],
    "babelrc": false,
    "moduleIds": false
};

gulp.task("js", () => gulp.src("source/**/*.js")
    .pipe(gulp_sourcemaps.init())
    .pipe(gulp_babel(BABEL_CONFIG))
    .pipe(gulp_amd_util.bundle({
        moduleRoot: "my-app",
        keepSource: true,
        outputPath: "my-app.bundle.js"
    }))
    .pipe(gulp_sourcemaps.write("."))
    .pipe(gulp.dest("dist"))
);

Options

sort (obsolete if calling bundle since 0.2.1):

  • moduleRoot: defines the base module id. Assuming a moduleRoot: "my-company/my-app", then a module defined in form/input.js will become "my-company/my-app/form/input" after the transformation.
  • moduleIds: if it's true, the module ids are added/fixed not only in the bundle, but in the individual files as well.
  • debug: produces more verbose logs

bundle:

  • moduleRoot: defines the base module id. Assuming a moduleRoot: "my-company/my-app", then a module defined in form/input.js will become "my-company/my-app/form/input" after the transformation.
  • outputPath: the file to write the bundle to.
  • keepSource: if true, the original files included in the bundle are kept after the transformation.
  • style (obsolete since 0.2.1): style of the bundle. The accepted values are: "dojo", "requirejs".
  • debug: produces more verbose logs