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

opsmap

v0.1.0

Published

Map of runnable interdependent operations

Downloads

5

Readme

opsmap Build Status Code Climate

Map of runnable interdependent operations

NPM

Example

var OpsMap = require('opsmap');
var UserModel = require('./models/user.js');
var BlogModel = require('./models/blog.js');

// declare map of interdependent operations
var blog = new OpsMap('blog');

blog.set('username', 'edinella'); // already resolved values can be setted

blog.op('user', function() {
  return UserModel.findOne({username: 'edinella'}).exec(); // returns a promise
});

blog.op('userPosts', function(user) {
  return BlogModel.find({author: user.id}).exec();
});

// run userPosts operation, returns a promise
blog.run('userPosts').then(yep).fail(nope);

// handle results
function yep(result) {
  console.log(result);
}

// handle errors
function nope(err) {
  console.error(err);
}

How to use

Install with NPM:

npm install --save opsmap

Then require it:

var OpsMap = require('opsmap');

API

constructor(alias): create a new OpsMap with an alias

To produce the instance, OpsMap should be called with new operator.

var report = new OpsMap('report');

set(token, value): defines a value for injection (alias: setCache)

Register the final value.

report.set('dateFormat', 'DD/MM/YYYY HH:mm:ss');

op(token, factoryFn): defines a operation that generates a value for injection (alias: operation)

To produce the instance, factoryFn will be called once (with instance context) and its result will be used.

The factoryFn function arguments should be the tokens of the operations that we need resolved here.

report.op('data', function(filters){
  return MyModel.find(filters).exec();
});

run(token): runs an operation, returns a promise

If any operation throws an error or gets rejected, and you omit the rejection handler, the execution will be stopped and error would be forwarded to this resultant promise.

// result is a promise
var myStats = report.run('stats');

// handle results
myStats.then(function(result) {
  console.log(result);
});

// handle errors, including those unhandled from inside operations
myStats.fail(function(err) {
  console.error(err);
});

Inspiration

Angular.js DI

githalytics.com alpha