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 🙏

© 2026 – Pkg Stats / Ryan Hefner

trigger-puller

v1.21.0

Published

Trigger qualifier/handler

Readme

Trigger Puller Architecture

Trigger puller architecture Password: lx123

Test Harness

npm start will run the test harness, which accepts POST requests with a body of the form

{
  "lxMessage": {...},
  "parameters": {...}
}

Where lxMessage is the triggering event, and parameters is the extensions install.

Example

The following example will trigger an email reaction.

{
  "lxMessage": {
    "subject": "recordChangePostCommit",
    "message": {
      "contents": {
        "record": {
          "id": 12732137,
          "apiName": "beer"
        },
        "priorState": {
          "name": "Coopers Stout",
          "unit_count": 21,
          "gluten_free": { "tag": "true", "value": {} },
          "foo": "bar"
        },
        "changeSet": {
          "unit_count": 18
        }
      }
    }
  },
  "parameters": {
    "args": {
      "field-unit_count": {
        "fieldApiName": "unit_count",
        "resolver": "recordField"
      },
      "email": {
        "html": "Didja get that thing I sent you?",
        "from": "Christie",
        "text": "Didja get that thing I sent you?",
        "subject": "That thing I sent you",
        "recipients": "[email protected]"
      }
    },
    "condition": {
      "qualifier": "bogan",
      "expression": {
        "expressions": [
          {
            "operands": [
              {
                "::argId": "field-unit_count"
              },
              20
            ],
            "operator": "<="
          }
        ],
        "operator": "&"
      }
    },
    "subject": "recordChangePostCommit",
    "context": {
      "record": {
        "apiName": "beer"
      }
    },
    "name": "Unit Count Low",
    "description": "Sends an email when unit count drops below threshold.",
    "reactions": [
      {
        "handler": "email",
        "argId": "email"
      }
    ],
    "id": "triggerpullerb0625452cadc4ce0aa75cef02427f606"
  }
}

Types

We're not flow typed yet, but for documentation's sake.

type LxMessage = {
  subject: string,
  message: Object
}

type Condition = {
  qualifier: 'bogan' | 'alwaysTrue',
  expression?: Object
}

type Reaction = {
  handler: 'dump' | 'email',
  argId?: string
}

type Trigger = {
  id: string,
  args: Object,
  name: string,
  subject: 'recordChangePostCommit',
  condition: Condition,
  reactions: Array<Reaction>
}

Publishing to trigger-puller

After merging your branch on Github, it doesn't automatically "deploy" once circle finishes building master. You also need to publish to extensions.

  1. On your local, switch back to master branch of trigger-puller and run git pull
  2. Run npm i -g @lanetix/lxt. This is the extensions cli found here
  3. Run npm version minor (This can be major, minor, patch)
  4. Run lxt publish. It will ask for your Lanetix login credentials. Input them.
  5. Finally, git push to update the version in github.
  6. Validate your code changes 1) by testing in production and 2) looking up the extensions table in dynamoDB to see the new version is indeed published, and it is at the @latest. Here is the link to the dynamoDB extensions table