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

rulerx

v2.0.0

Published

Reactive Rule Engine

Downloads

4

Readme

Build Status Coverage Status

RuleRx

A library for rule evaluation written in Typescript that enables the reactive approach (with Rx.js) on business objects.

The Reactive RuleEngine library

The engine allow evaluating rules that are defined as object streams representing a scenario. Rules configuration leverage JsonPath specification in order to allow traversing objects nodes without requiring a predefined schema.

No predefined schema does not mean you can't have type-safety! you can set the type of any given context on which the rules will be evaluated.

Rules are evaluated among observables of the business context which produces an observable stream of emitted results whenever there's a match.

Context observables can emit new values over time, and the rules will be streamed any time your business context changes.

Features

  • Schemaless object nodes traversal using JsonPath
  • Support custom operators and embedded operators
  • Support for serialized rules to be evaluated
  • I/O as observable streams (Rx.js)
  • Easy rule definition for business/functional approach
  • Supported for both Node.js and the Browser

Getting started

Installing the library:

with npm:

npm i rulerx

Writing basic rules

First, let's define one model of our context

interface Person {name: string; surname: string }

Then we define our rule sets

const rules: RuleSet<Person>[] = [
       {
         all: [ // match all these rules
           {
             fact: 'name is equal to Jhon', // describe the fact
             operator: equal, // the operator
             path: '$.name', // the jsonPath of the node
             value: 'Jhon' // the expected value
           },
           {
             fact: 'surname is equal to Doe',
             operator: equal,
             path: '$.surname',
             value: 'Doe'
           }
         ]
       }
     ]

Create some Persons observables for the context

const persona: Person = {
    name : "Jhon",
    surname: "Doe"
}
const persona2: Person = {
    name : "Ada",
    surname: "Lovelace"
}
const observable: Observable<Person> = of(persona);
const observable2: Observable<Person> = of(persona2);

Now it's time to evaluate our context!

new RuleRx<Person>()
      .evaluate(rules, observable, observable2)
      .pipe(mergeAll())
      .subscribe(next => {
            console.log(next.element);
      })

Since only Jhon Doe match all the rules (equal $.name && equal $.surname) this will emit:

{
    name : "Jhon",
    surname: "Doe"
}