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

trivial-rules

v0.0.6

Published

Create JSON objects for a given situation from a manifest of rules

Downloads

28

Readme

Trivial Rules

A simple NodeJS rules engine to create RegisterItem JSON from events. This library is not responsible for saving the RegisterItems, only producing them.

Installation

npm install trivial-rules

Usage

Generating an application from a manifest file


// Import the Generator class
import { Generator } from 'trivial-rules'

// CommonJS is also supported
// const { Generator } = require('trivial-rules')

// Definte a valid manifest JSON
const manifestJSON = {
  "app_id": "a1",
  "manifest_version": 3,
  "definitions": [],
  "rules": [
    {
      "name": "Order Shipped",
      "conditions": "initialPayload.event_name == 'order.shipped'",
      "outputs": [
        [
          {
            "from": "3.01",
            "to": "amount"
          },
          {
            "from": "`Order shipped for ${initialPayload.name}`",
            "to": "description"
          }
        ]
      ],
      "enabled": true
    }
  ]
}

// Create a new generator instance and run the main function
const destinationPath = './output'
const generator = new Generator(manifestJSON, destinationPath)
await generator.main()

// Files will be written to the destination folder
// ./output/rules.js
// ./output/manifest.json
// ./output/definitions.js

Applying rules to an event

// The Rules class will be written to the destination folder, you can now import and apply with

import { Rules } from './output/rules.js'

// CommonJS:
// const Rules = require(`./output/rules.js`)

const event = { event_name: 'order.shipped' }
const out = await Rules.apply(event)
// The result is an Promise that resolves to an Array of objects the Rules logic produced.
// Example:
[
  {
    amount: 3.01,
    description: 'Order Shipped',
  }
]

Handling Errors

If an error is encountered applying rules, none of the rules will be applied and the error will be returned. This is to ensure that the rules are applied in consistently. This way, if an event fails, it can more predictable be re-played, with confidence that the rules for the event have not been partialy applied.

As such, it is the event processor's responsibility to handle the error and decide how to proceed.

Running Tests

Tests are provided via vitest. To run the tests, simply run:

npm run test

Publishing

This package is written in ESM and is converted to CJS using Rollup. This will recreate index.cjs.

Publishing steps:

  1. Run Rollup
npx rollup -c
  1. Bump the verson number in package.json.

  2. Update the changelog to describe the changes.

  3. Commit the changes, create a PR, and merge to main.

  4. Finally, publish to npm from main:

npm publish