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

@marknotton/notifier

v1.2.2

Published

Manage CLI and popup notifications messages.

Downloads

5

Readme

Notifier

Made For NPM Made For Gulp

Manage CLI and popup notification messages.

Installation

npm i @marknotton/notifier --save-dev
const notifier = require('@marknotton/notifier');

Usage

gulp.task('someTask', () => {
  return gulp.src([...])
  .pipe(plumber({errorHandler: notifier.error }))
  .pipe(concat('ccombined.js'))
  .pipe(gulp.dest('/some/location/'))
  .pipe(notifier.success())
});

Options

| Option | Type | Default | Details | |--|--|--|--| | project | String | Package.json 'name' | Project name. Will appear as a subheading. | | exclusions | String | '.map' | Files that match any part of this string will be excluded from any notification | | prefix | String | - | String to add before the notification message | | suffix | String | - | String to add after the notification message | | popups | Bool | true | Prevent popups from showing. Console logs will still be rendered. Defaults to false on non 'dev' environments. | | success | String | | Icon to use on success messages. Can be relative to the project folder or an absolute URL. An attempt will be made to look for a 'icon.png' in your projects root directly. | | error | String | | Icon to use on error messages. Can be relative to the project folder or an absolute URL | | messages | String | Files compiled successfully | The message you want to display. This can be a shorthand name that references an object key defined in the defaults function (see below) | | extra | Array/String| - | Manually add extra files to log out, regardless of whether they are actually part of the stream |

A string will be defined as the message or message shorthand.

notifier.success('js', { project : 'My Project', ...})

Notice the use of a shorthand name as the first parameter. This will look for the keys in the default settings object. So you can list all your messages in one place.

Defining your default settings

You can preset the above options with the settings function. This will be refereed as your default options for every notifier instance.

notifier.settings({
  project : 'My Project,
  success : 'images/icon.png',
  exclusions:'.map',
  messages  : {
    js      : 'Javascript files compiled!',
    sass    : 'Looking gooooood!'
  }
});