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

rulesenginejs

v1.27.0

Published

A simple front-end rules engine

Downloads

36

Readme

RulesEngineJS

What is a rules engine?

A rules engine decouples the workflow logic from other components. This is done by defining the rules once, and having components listen for events triggered by a rule. This reduces repeated code in components and makes it easier to update existing rules. Rules engines also reduce repeated code in the rules logic, by allowing rules to be composed and conditioned on other rules.

How does it work?

The rules engine has three parts: facts, rules, and events.

When facts are updated in the rules engine, its rules are evaluated. If a rule passes (resolves or evaluates to true), it triggers any events that has been defined in that rule. Any listeners which are listening for that event will then be triggered.

Why should I use this?

  • Supports async rules
  • Supports rule priorities
  • Supports event listeners
  • Supports nested conditions (all, any)
  • Supports negative conditions (!)
  • Small (9kb minified)
  • Efficient (caching, early exit)
  • ES5 compatible
  • Depends only on jQuery
  • Easy to use

If you are developer in need of a lightweight rules engine, this is it.

<script src="rulesengine.min.js"></script>

How do I use it?

  1. Define a rules engine.
var RE = new RulesEngine();
  1. Add rules.
RE.addRules([
  ['active', function(facts) {
      return facts.status === 1
  }],
  ['approved', function(facts) {
      return facts.status === 2
  }],
  ['not_approved_or_active', null, {
      conditions: {
          all: ['!approved', '!active']
      },
      events: 'is_editable'
  }]
]);
  1. Add listeners.
RE.on('is_editable', 'disable_button', function() {
$('.edit-button').removeClass('disabled');
});
  1. Update facts.
RE.updateFacts({status: 3});
// is_editable event triggered: edit-button is now enabled
  1. Evaluate just a single rule.
RE.evaluate('active', {status: 1})
.done(function() {
  alert('Status is active');
})
.fail(function() {
  alert('Status is not active');
});
// alerts "Status is active"

For more examples, refer to the tests.

What methods are available?

RE.updateFacts(facts) // returns $.Deferred()
RE.addRule(name, evaluator, options)
RE.addRules([[name, evaluator, options], [name, evaluator, options] ...]
RE.deleteRule(name)
RE.addEvent(name)
RE.addEvents([name, name ...])
RE.emit(event)
RE.on(event, name, handler)
RE.run() // returns $.Deferred()

RE.evaluate(facts, event) // returns $.Deferred()
// Evaluates against a set of facts to see if an event is triggered
// Triggers no other events and does not modify state (idempotent)

// ... more methods under the hood ...