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

noti-fire-js

v0.0.1

Published

A simple notification library for managing technical debt

Downloads

6

Readme

Noti-fire

A simple notification library for managing technical debt.

The cheesey sales pitch

Are you tired of this:

var library = require('library');

library.configure({
    property: true, // Have to pass this property for "function" to work see https://github.com/org/repo/issues/123
})

var result = library.function();

Does this ever happen to you:

var library = require('library');

// Won't need to use this once this lands https://github.com/org/repo/issues/321
library.function();

Ever been told 'we will look into fixing it later' and then never got round to it?

Then you need Noti-fire!

Functionality

Notifire provides a simple interface that processes comments and fires notifications once the conditions are met (see what I did there?). Noti-fire can then be run during a build and will fail if there are any resolveable issues within your code. A Noti-fire notification is configured using comments:


// noti-fire NOTIFIER_NAME [PARAMS]

Noti-fire then scans all code files for these notification, checks to see weather any of the conditions have been met to resolve this issue and fails if this is the case. There are currently 3 build in notifires:

Date

Review this code once a specific date has passed:


// Needs reviewing
// noti-fire DATE 11/11/3011
const hackyFunction = function() {
    // Some terrible code here
} 

Once the date has passed notifire will then start failing, letting you know that this code needs to be addressed.

Github

Review this code when a specific Github issue is resolved:


// Once [FEATURE] lands we won't need this anymore
// noti-fire GITHUB ISSUE [ORG] [REPO] [NUMBER]
const hackyFunction = function() {
    // Some terrible code here
} 

Once this issue is closed notifire will then start failing, letting you know that this code needs to be addressed.

Jira

Review this code when a specific Jira issue is at a given state:


// Once the middleware team implement [FEATURE] we won't need this
// noti-fire JIRA [NUMBER] [STATUS]
const hackyFunction = function() {
    // Some terrible code here
} 

Once the Jira story is at the status specified noti-fire will start failing, letting you know that this code needs to be addressed.