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

libumd

v0.9.0

Published

Wraps given JavaScript code with UMD

Downloads

5,302

Readme

build status

libumd - Wraps given JavaScript code with UMD

Usage

var umdify = require('libumd');

...

var result = umdify(js, options);

libumd doesn't guarantee pretty formatting. It is better to use something like js-beautify to deal with that.

Options

{
    template: 'path to template or template name', // defaults to 'umd'
    amdModuleId: 'test', // optional AMD module id. defaults to anonymous (not set)
    globalAlias: 'alias', // name of the global variable
    deps: { // dependencies
        // use default only if the module name and the variable the module will be injected with is the same
        'default': ['Foo', 'Bar'],
        // additionally define these if the module name differs from the variable with which it will be used
        // note how we can map dependencies to specific parameters
        amd: ['foo', {'lodash': '_'}],
        cjs: ['foo', 'bar']
    }
}

Check out the demo.js

Default Templates

The library comes with a couple of UMD variants at /templates. In addition you may use one of your own as long as it is formatted using Handlebars syntax and follows the same naming conventions as the ones provided with the project.

Testing

Make sure PhantomJS is installed and it's within your PATH. Hit npm test after that. If the UMD wrapper fails to run against the headless browser, you'll know.

Contributors

  • Stéphane Bachelier - Use existing objectToExport instead of hardcoded value returnExportsGlobal for AMD.
  • Simon Harte - Made the documentation clearer about the correct usage.
  • Valerii Zinchenko - Allowed dependency name to contain a dash. #17
  • @timeiscoffee - Updated UMD templates to the current scheme. #18

License

libumd is available under MIT. See LICENSE for more details.