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

feathers-trigger

v3.0.1

Published

Add triggers and actions to your feathers app.

Downloads

157

Readme

feathers-trigger

NOTE: This is the version for Feathers v5. For Feathers v4 use feathers-trigger v0

npm GitHub Workflow Status Code Climate maintainability Code Climate coverage libraries.io npm GitHub license

Documentation

For more information, please have a look at the docs: https://feathers-trigger.netlify.app/

Installation

npm i feathers-trigger

Usage

Imagine you want to notify users when a post gets published.

How can this be done? In this example a post has a publishedAt property which shows when a post was published. A post with publishedAt === null means that the post is not published yet. A post can be created as a draft which is not published.

But how do you know when a post gets published? Sounds silly, but there are three possibilities:

  • A post gets created with publishedAt: { $ne: null }.
  • A post gets updated by data publishedAt: { $ne: null }, it had publishedAt: null before and the result really has publishedAt: { $ne: null }.
  • A post gets patched by data publishedAt: { $ne: null }, it had publishedAt: null before and the result really has publishedAt: { $ne: null }.

How can this be accomplished?

  1. Check context.data for publishedAt: { $ne: null } and if that's not true, the subscription is not true.
  2. Check if the post in the database has publishedAt === null and therefore is not published yet. You need to check that in a before hook. If that's not true, the subscription is not true.
  3. Check if the context.result really has publishedAt: { $ne: null } (maybe it's handled by another permission hook, or something). If that's not true, the subscription is not true.
  4. If all three checks are true, run the notify function.

It's up to you how you define the notify action. For the example above the solution with feathers-trigger looks like the following:

// posts.hooks.js
import { trigger } from 'feathers-trigger';

const notifyPublished = trigger({
  conditionsData: { publishedAt: { $ne: null } },
  conditionsBefore: { publishedAt: null },
  conditionsResult: { publishedAt: { $ne: null }},
  action: ({ item }, context) => {
    return context.app.service('/notify').create(item);
  }
});

export default {
  before: {
    create: [ notifyPublished ],
    update: [ notifyPublished ],
    patch: [ notifyPublished ]
  },
  after: {
    create: [ notifyPublished ],
    update: [ notifyPublished ],
    patch: [ notifyPublished ]
  }
}

For more advanced examples, please have a look at the docs

Testing

Simply run npm test and all your tests in the test/ directory will be run. It has full support for Visual Studio Code. You can use the debugger to set breakpoints.

Help

For more information on all the things you can do, visit FeathersJS.

License

Licensed under the MIT license.