Release 5.0.1

Fixes:

• Issue #60: ESLint dependencies breaking tests

Adds:

• Title prop thanks to work of PR #59 by @lacerda

Version 5.0.0

Fixes:

• Issue #48
• Issue #47

Breaking Changes:

• Instead of passing in one style object, there are now several objects: barStyle, actionStyle and activeBarStyle. These objects work as expected, e.g., barStyle are styles applied to the snackbar. If style has a value of false, inline styles are entirely disabled.

Version 4.3.0

Adds:

• You can use both a string and a React component as the value for the message prop. This enables one to pass a React element to the notification as a message, without throwing a warning.

Thanks to @SebT for the PR.

Version 4.2.0

Fixes:

• Issue #43

Thanks to @sergiofm for the PR.

Version 4.1.1

Fixes:

• Issue #44, which prevented the components from easily being imported 🚒

Note this is a breaking change. The components are now exported as an object. For example

// ES2015+
import { Notification, NotificationStack } from 'react-notification';

// ES5
var Notification = require('react-notification'). Notification;
var NotificationStack = require('react-notification').NotificationStack;

Version 4.0.0

Adds:

• Support for stacks of notifications. Whoooohooo! 🙌
• Thanks to @meta-meta for the original code and PR for the notification stack.

Version 3.0.0

Adds:

• New tests
• React 0.14.x support

Version 2.3.0

Fixes:

• Using a boolean value for the action prop would cause a warning
• Notifications dismiss with the value of the previous props dismissAfter instead of the next props value

Adds:

• You can use a custom class name
• You can use a custom active class name

Thanks to the following GitHub users for the PRs and bug reports:

• @SebT
• @dentrado
• @idolize

Version 2.2.0

Adds:

• GPU acceleration for the transition thanks to @dallaspersson

Version 2.1.0

• Including the action={false} prop on the component will remove the action from the notification bar