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

aster-umd

v0.2.0

Published

Wrap code to UMD with aster.

Downloads

16

Readme

aster-umd

NPM version Build Status

Wrap code to UMD with aster.

Usage

First, install aster-umd as a development dependency:

npm install --save-dev aster-umd

Then, add it to your build script:

var aster = require('aster');
var concat = require('aster-concat');
var umd = require('aster-umd');

aster.src('src/**/*.js')
.map(concat('superLib.js'))
.map(umd({
  deps: [
    {name: 'jquery', globalName: 'jQuery'},
    'jade',
    {name: 'lodash', globalName: '_', amdName: '../lodash'}
  ]
  //, exports: 'superLib' - no need to set explicitly in this case
}))
.map(aster.dest('dist'))
.subscribe(aster.runner);

API

umd(options)

options.exports

Type: String Default: generated from filename (i.e. superLib/smth.js => superLib.smth).

Global name (may be namespaced) for exported object.

options.fromGlobal

Type: Boolean Default: false

When set to true, identifier from options.exports is assumed to be already set in code and will be used as exports.

When set to false (default), value from top-level return statement will be used instead.

options.deps

Type: Array(String | Object) Default: []

External dependencies array. Each item may be either string or extended object in following form:

{
  name: '' // default name for any properties that aren't set
  globalName: '', // global name for dependency
  paramName: '', // parameter name for the wrapper function (defaults to `globalName`)
  amdName: '', // module name for the AMD dependency
  cjsName: '' // module name for the CJS dependency
}

For example, from:

[
    {name: 'jquery', globalName: 'jQuery', paramName: '$' /* , cjsName: ..., amdName: ... */},
    'jade',
    {name: 'lodash', globalName: '_', amdName: '../lodash'}
]

...you would get:

(function(root, factory) {
    if (typeof define === 'function' && define.amd) {
        define(['jquery', 'jade', '../lodash'], factory);
    } else if (typeof exports === 'object') {
        module.exports = factory(require('jquery'), require('jade'), require('lodash'));
    } else {
        root.test = factory(root.jQuery, root.jade, root._);
    }
}(this, function($, jade, _) {
    // ...
}));

License

MIT License