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

jsre

v0.6.0

Published

JSON based rules engine

Downloads

3

Readme

Build Info

Statements Functions Lines Branches

JSon Rules Engine

There are several JSON rules engines avaialable so why build another one? As usual, the ones out there were not really a good fit. So this package is based on the following focus:

  1. Derived facts should be computed to the document of inspection before the business rules are run
  2. Use the latest ES7 based capabilities in the implementation to eliminate unnecessary boiler plate
  3. Focus on inspecting a single large JSON object that could come back from an API or an object moving through a streaming platform
  4. Allow for the use of YAML, it is just more concise
  5. Lean on AJV for rule specification validation
  6. Lean on lodash for a lot of heavy lifting
  7. Like other rule engines, re-use the rules data structure to put the results of calculation to make it easier to diagnose failures
  8. In the results returned, returned a focused list of errors to simplify diagnosing errors

Example

test('example rule pass', () => {
  const testDocument = {
    prop1 : {
      prop2 : {
        prop3 : 1
      }
    }
  };
  
  const rules = [
    {
      conditions: {
        all: [
          {
            operator: "equal",
            lhs: 1,
            rhs: {
              path: "prop1.prop2.prop3"
            }
          }
        ]
      }
    }
  ];
  
  const engine = new Engine( { rules } );
  const results = engine.run( testDocument );
  expect(results).toHaveProperty('success');
  expect(results.success).toBe(true);
});

Operators

Operators are very easy to add and are kept pluggable in a directory called operator

Requests

Requests for added functionality are welcome and will be implemented without asking for pull requests or $ =)

Docs

Documentation