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

consequences

v0.1.1

Published

Consequences provides the scaffolding for automation.

Downloads

2

Readme

Consequences

Consequences provides the scaffolding for automation.

This is achieved by loading globally installed addons, automatically performing actions based on a set of rules and triggers, and providing an HTTP interface to inspect and update the state of the application.

Concept

On the surface Consequences does not offer a lot. From a user perspective it is comprised on:

  • Variables - A value that can change, e.g. the brightness value of a light bulb, or the status of a motion sensor
  • Condition - A rule that can be evaluated to either true of false, e.g. "the brightness of the lounge light bulb is 0"
  • Action - Something that will change the state of the application, e.g. "set the brightness of the lounge light to 45%"

Chains

With these basic concepts "chains" can be created, e.g. "when the lounge motion sensor detects motion, turn the lounge light bulb up to 65%".

Chains support multiple conditions and multiple branches, allowing for complex setups to be created with minimal effort, e.g.:

Motion Sensor (variable)
└── "detected motion" is true (condition)
    └── Lounge light bulb is off (condition)
        ├── The sun has set (condition)
        │   ├── Set the lounge light bulb's temperature to warm (action)
        │   └── Turn the lounge light bulb up to 70% (action)
        └── The has not set (condition)
            ├── Set the lounge light bulb's temperature to soft (action)
            └── Turn light bulb up to 30% (action)

Status

This project is currently under development and is considered unstable. Until a stable 1.0 version is released I would recommend you do not use this project, unless you wish to contribute.

Roadmap

  • [X] Provide TypeScript types for addon authors
  • [X] Load globally install addons
  • [X] Provide a web API to retrieve and create addons
  • [X] Provide a web API to retrieve the status of and modify variables
  • [ ] Provide a web API to setup "chains" e.g. condition[1-*] => action
  • [ ] Create a web GUI (in another project)

License

Consequences is released until the MIT license. See the LICENSE file for the full license.