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

react-cheers

v0.1.0

Published

A toast-management component for React without any dependencies, cheers!

Downloads

4

Readme

React Cheers

A zero-dependency, extensible notification system built with the React 16.3 Context API.

Installation

  1. npm install --save react-cheers

  2. Install Provider & Composer component as early as possible.

import { Provider, Composer } from 'react-cheers';

const App = (
  <Fragment>
    <Provider>
      <MyApplication />
      <Composer />
    </Provider>
  </Fragment>
);

reactDom.render(<App>);
  1. Access the notifications state & actions from within any component in your React tree using either:
  • Option 1: Use the withNotifications HoC to automatically pass all context props to your component.
import { withNotifications } from 'react-cheers'

const MyComponent = ({
  notifications<Array>,
  expire<Function>
  dispatch<Function>
  }) => (
    <button onClick={dispatch(notification<Notification>)}>Send!</button>
  );

export default withNotifications(MyComponent);
  • Option 2: Access the Context directly to select specific props. React Context uses "render props" to emit state.
import { Context as NotificationContext } from 'react-cheers'

const MyComponent = () => (
  <NotificationContext>
    {({
        notifications<Array>,
        expire<Function>
        dispatch<Function>
    }) => (
      <button onClick={dispatch(notification<Notification>)}>Send!</button>
    )}
  </NotificationContext>
);

export default MyComponent;

Usage

Notification

A notification object is made up of the following parameters.

  • kind : enum('notification', 'success', 'error', 'warning') - Denotes the kind of notification, primarily used for styling
  • message : string - The message contents
  • id (optional) : number | string - Optionally specify an ID. If null, falls back to dateTime. (NOTE: This library prevents dispatching notifications with duplicate Ids)
  • expires (optional) : number - The time in ms until notification is expired. If null, notification will not auto-dismiss.

Props

This library provides three primary mechanisms for interacting with notifications.

  • notifications : Array<Notification> - The array of current notifications
  • dispatch(Notification) : Function - The action to create/dispatch a new notification
  • expire(Id) : Function - the action to expire/dismiss/destroy a notification

Configuration Options

  • defaultExpires can specify a default expires time for all notifications
  • defaultKind can specify a default "kind"
<Provider defaultExpires={8000} defaultKind={'error'}>

Contributing

WIP

Tests

WIP