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

udefine

v0.8.9

Published

Define an UMD module like an AMD module and use it (almost) anywhere

Downloads

52

Readme

udefine

Build Status Dependency Status devDependency Status

Define an UMD module like an AMD module and use it (almost) anywhere

Why would you need it?

  • You are writing that needs to available in Node.js, AMD and/or as global objects
  • You need some kind of basic dependency resolution for your modules

Features

  • Provides a handy function wrapper for UMD modules
  • Same fuction signature as AMD modules
  • No need for boilerplate definitions
  • Less than 0.6 kB minified and gzipped (might increase a bit, but I'll keep it under 1kb)

Usage

(function(root) {
  // This definition only needs to be done once, not per module
  root.udefine.globals.jquery = this.jQuery;
})(this);

udefine('mymodule', ['jquery'], function($) {
  $.fn.myModule = function() { /* ... */ };
});

If an AMD module loader like RequireJS has been integrated and configured, it will resolve through the AMD loader.

Alright, that's really great for jQuery modules. But what if you want to bind a module the global namespace if there is no AMD or CommonJS? Just define where the module should be injected to and udefine will do the rest:

udefine.configure(function(root) {
  udefine.inject['myothermodule'] = {
    root: root,
    name: 'myOtherModule'
  };  
});

udefine('myothermodule', function() {
  return {
    a: function() { return 5; },
    b: 2
  };
});

// root.myOtherModule now is an object with the properties a and b.
// (In a non-AMD or non-CommonJS environment.)

CommonJS pitfalls
If using module.exports for exporting your modules on CommonJS, it does not export correctly on udefine 0.8.x. (Exporting with exports using the injection API works though.) To counteract this behavior, you would need a bit of boilerplate code:

(function() {
  udefine.configure(function(root) {
    this.globals(function() {
      udefine.inject['mycoolmodule'] = {
        root: root,
        name: 'myCoolModule'
      };  
    });
  });


  udefine('mycoolmodule', function() {
    return {
      a: function() { return 5; },
      b: 2
    };
  });

  if (udefine.env.commonjs) {
    udefine.require('mycoolmodule', function(myCoolModule) {
      module.exports = myCoolModule;
    });
  }

}).call(this);

// root.myOtherModule now is an object with the properties a and b.
// (In a non-AMD or non-CommonJS environment.)

udefine is not and does not replace a module loader. It is primarily intended for developers who want their library to target AMD modules, CommonJS modules and/or the classic way of binding object to the global window object.

For more examples, take a look at the examples folder.

License
This is public domain. See UNLICENSE.md for more information.

Bitdeli Badge