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

zpm

v0.2.4

Published

The end of umd package manager for web.

Downloads

28

Readme

zpm


NPM version Build Status Coverage Status

The end of umd package manager for web.

You can write code on commonjs, and build it for anywhere.

Diff

long time ago, if you want code run in browser for anywhere, you need write code like this:

(function(window){
  if (window.Mod){
    return window.Mod;
  }

  function factory(detector){
    var Mod = {};
    Mod.method = function(){
      return detector.os.name + "/" + detector.os.version;
    };

    return Mod;
  }

  if ("function" === typeof define && (define.cmd || define.amd)){
    define(function(require, exports, module){
      module.exports = factory(require("detector"));
    });
  } else {
    window.Mod = factory(window.detector);
  }
})(this);
  • In non-cmd, non-amd, you must use global variable.
  • You must manager dependencies by hand via global variable.

Now you just write code on CommonJS, zpm will build it to umd for anywhere in browser:

var detector = require("detector");

var Mod = {};
Mod.method = function(){
  return detector.os.name + "/" + detector.os.version;
};

// If you donot want, global variable is not necessary.
window.Mod = Mod;
module.exports = Mod;

And you may want use spm for write, debug, test and publish you source code.

Install

$ npm install -g zpm

Usage

$ zpm build

Configure in package.json

{
  "zpm": {
    "output": {
      "umd-moudle-a.js": "commonjs-module-source-code-a.js",
      "umd-moudle-b.js": ["commonjs-module-b.js", "commonjs-module-c.js"]
    },
    "dependencies": {
      "jquery": "1.7.2"
    }
  }
}

If no zpm infomation in package.json, zpm build use spm infomation.

{
  "spm": {
    "main": "index.js",
    "dependencies": {
      "jquery": "1.7.2"
    }
  }
}