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

@verbenergy/verb-rules-engine

v1.4.0

Published

> [JSON Rules Engine](https://github.com/cachecontrol/json-rules-engine) extension for Verb development

Downloads

5

Readme

Verb Rules Engine

JSON Rules Engine extension for Verb development

Testing Changes Locally:


Linking npm package

  1. commit your changes
  2. npm run build
  3. (in this repo) sudo npm link
  4. (in other project) npm link @verbenergy/verb-rules-engine
  • To un-link:

  1. (in other project) npm unlink --no-save @verbenergy/verb-rules-engine
  2. (in this repo) npm unlink

Getting things up and running

  1. run event-platform heroku local
  2. run workflow-service heroku local -f Procfile
  3. run crm v1 heroku local web

Triggering an event

  1. see Notion on how to test in staging

Publishing Instructions:

Follow normal workflow for code changes. After PR is merged:

  1. run npm version {major, minor, patch} depending on the change type.
  2. run npm run build
  3. run npm publish

Trouble publishing?

  1. Make sure you're set up as a member on the package.
  2. Generate a new access token under your account in npm with publishing rights.
  3. Find .npmrc hidden file in your user folder and replace authToken(s) there with your new one.
  4. Replace your new token with old one (might have trouble installing on other repos if you use new one)