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

lamd

v0.5.2

Published

Local Asynchronous Module Definition library

Downloads

24

Readme

lamd

Local Asynchronous Module Definition library

Build Status

NPM

About

lamd is an "offline" AMD implementation, designed to provide require and define methods for a local set of modules. require makes no remote calls, and expects everything to be defined by the corresponding define method.

lamd uses simple wrapper functions, along with setImmediate, to execute dependency factories and callbacks with decent performance (it used to use Promises). No timers or intervals are used, unless setImmediate is not available (make sure to polyfill for best performance!).

Why?

lamd was built as a result of experiences while working at Kiosked - Kiosked's front-end script bundles its entire library for delivery to the client, and makes use of AMD to define its modules. Because no modules are requested from remote sources, a clean form of local-style AMD was required.

Usage

define

You can define a module by doing the following:

define("my-module", function() {
	return {
		myMethod: function() {
			return true;
		}
	};
});

// or, for example:

define("my-module", ["my-dependency"], function(dep) {
	return function() {
		return dep();
	};
});

define's method signature is define(id[, dependencies], callback), where:

  • id is the ID of the module, which is required
  • dependencies is an optional string or array or dependent module IDs
  • callback is a required callback function which takes the dependent module outputs as parameters

require

require can be viewed as the same as the define method, but without an ID.

require's method signature is require(dependencies[, callback]), where:

  • dependencies is a string or array of required module outputs
  • callback is a callback function which takes the required dependency outputs as parameters

require can return the defined module instance if it's ready: simply require only 1 module and do not provide a callback:

var MyModule = require("MyModule");

require will return undefined if the module is not ready. Remember that define works asynchronously.

Using this library

lamd writes lamd to the global object (or current context), so you can access its methods like so:

lamd.define 		// Function
lamd.require 		// Function
lamd.setImmediate   // Function

lamd's setImmediate may resolve to setTimeout(fn, 0) if a setImmediate polyfill is not available. I recommend using this one by YuzuJS.