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

browser-notification

v3.0.0

Published

Small library built around browsers native Notification-API adding useful default behaviour.

Downloads

145

Readme

browser-notification

Tiny library built around browsers native Notification-API with some useful default behavior.

Demo

browser-notification does just a few things

  • Look for browser support and ask for user permission when initialized.
  • Clicking a notification will focus the browser tab that fired the notification.
  • ignoreFocused - If browser tab is already focused notify() -call will be ignored. optional, default: true
  • For API ergonomics it's always possible to fire notify() since in case Notifications are not available it's just a no-op (does nothing).
  • cooldown - milliseconds before consecutive notification can be fired. optional, default: 0
  • timeout - milliseconds to wait before auto-closing notifications. optional, default: 0 (disabled)

Install

yarn add browser-notificaiton

or

npm install browser-notification --save

The library has no dependencies and size is less than 1kB (minified + gzipped). A UMD build is available in /dist of the npm package.

Usage

import {initNotifications, notify} from 'browser-notification';

// Check browser support, ask permission, initialize
initNotifications();
...
// Notify
notify('This is the title.', {body: '...and this is the body'});

Note - The underlying Notifications API for permission is async so if you want to initialize at the same time as firing notify(), you must first resolve the promise returned from initNotifications() to ensure initialization is complete, see API and example below.

API

initNotifications({options}) Create and setup the notifier object, asking for permission, returns a promise resolving a boolean indicating wheather notifications are available or not.

Default options:

{
  ignoreFocused: true, // ignore notify() -calls when browser tab is already focused.
  timeout: 0,  // Set a time (ms) > 0 to activate
  cooldown: 0,  // Set a time (ms) > 0 to activate
}

notify(title, {options}) Takes the same arguments at the native Notification API call returns the Notification object or null if notification was not sent. The Notification object can be used to attach event handlers onclick/onclose/onerror/onshow

Example of initializing and calling notify asyncronously. Also using timeout/cooldown feature

import {initNotifications, notify} from 'browser-notification';

initNotifications({
    timeout: 3000,  // Auto-close notifications after 3 sec
    cooldown: 3000,  // Ignore new notify calls for 3 sec
}).then(function(isAvailable) {
  notify('Ping!');

  if (isAvailable) {
    console.log('notification was sent');
  }
  else {
    console.log('notification was not sent');
  }
});