2.0.0-alpha.2 • Published 5 months ago

vue-toastify v2.0.0-alpha.2

Weekly downloads
404
License
MIT
Repository
-
Last release
5 months ago

Vue Toastify

last commit npm downloads minzipped size

I wanted a notification plugin which I can use by passing props from the server and can also be called at run time. With this component it's has just become super easy. It's easily extendable and customizable and it has no dependencies.

Check it out at Netlify

Requires Vue 2.2.0+

Quick start:

npm i vue-toastify

or with CDNs:

In your main js file:

import VueToastify from "vue-toastify";
Vue.use(VueToastify);

Then anywhere just call:

this.$vToastify.success("easy-peasy");

Settings

You may pass a settings object to the use statement like so:

Vue.use(VueToastify, {
    my: "settings"
});

or change any of the settings during run-time with the following

this.$vToastify.setSettings(settingsObject);

This will return the current settings after the updates.

To use the vue router supported features pass in the router to the use statement as the 3rd argument like so:

import routerLoadedWithRoutes from "./router";

Vue.use(VueToastify, {}, routerLoadedWithRoutes);

Available settings

settingtypedefaultdetails
singularBooleanfalseOnly allow one notification on the screen at a time, others will be queued up for showing later.
withBackdropBooleanfalseEnables backdrop to be shown.
backdropString"rgba(0, 0, 0, 0.2)"The rgba value for the backdrop.
positionString"bottom-right"Defines where the notifications should be showing on the screen. Available values are: "top-left", "top-center", "top-right", "center-left", "center-center", "center-right", "bottom-left", "bottom-center", "bottom-right"
errorDurationNumber8000The duration in milliseconds the error notification should be visible for.
successDurationNumber4000The duration in milliseconds the success notification should be visible for.
warningInfoDurationNumber6000The duration in milliseconds the warning and info notification should be visible for.
canTimeoutBooleantrueWhether the notifications disappears after the set time.
canPauseBooleantrueWhether the notifications can be paused by hovering over them.
hideProgressbarBooleanfalseWhether the progressbar should be shown on the notification or not.
defaultTitleBooleantrueWhether a default title should be shown if no title is supplied.
themeString"dark"What theme should be displaying. By default there's light and dark.
orderLatestBooleantrueWhether new notifications should display on top of the stack or not.
transitionString / ObjectnullIf string supplied this will apply the usual transition classes (eg.: .name-enter-active), if object supplied it expect a name and optionally a moveClass (this class has to use !important for its rules) attribute. The name will be applied as above. The move class applied when the notifications adjust their position.
iconEnabledBooleantrueIf set to false, no icon will be shown on the notification.
draggableBooleantrueWhether to enable dismissing the notification by dragging or not.
dragThresholdNumber0.75A number between 0 - 5 representing how far the notification should be dragged to dismiss.
baseIconClassStringnullIf string is set, this will be appended to every user supplied icon's class.
maxToastsNumber6Defines how many toasts should be visible at a time. Others are queued.
oneTypeBooleanfalseIf turned on, only toasts with unique mode/type will be show. Others are queued.

To fetch the current setting you may run the following which will return all the settings.

this.$vToastify.getSettings();

You may optionally pass an argument to the above to only get the value for that key.

Status

You can pass to the functions either a string for the body of the status and optionally a title for the second argument like so:

this.$vToastify.error("body", "title"); 

Or pass an object to the method:

this.$vToastify.info(stausObject);

The following properties can be set on the object:

propertytypedetails
bodyString/FunctionRequired parameter, you may pass html, JSX, or a function that returns JSX to this.
titleStringEnables pausing of the loader and the timeout on hover.
typeStringDefines what notification type should be showing available types: "success", "warning", "info", "error" defaults to "success". This can only be set if you're using this.$vtNotify() Alternatively you may use the methods: this.$vToastify.warning("more readable")
modeStringIf set the notification will be shown in the given mode: loader, prompt. Alternatively you may use the methods: this.$vToastify.loader("more readable")
urlString / ObjectIf set, clicking on the notification will take the user to the given location. If its a string and used with router and route not found this will be ignored. If giving an object then you can either define attributes of the anchor tag like: { href: "https//google.com", target="_blank" } or pass the object you would pass to the router.push() function.
iconString / ObjectIf set, this will be displayed instead of the default icons. If is a string the string will be assigned to the class unless it is an svg. If it is an object it may take the following attributes { tag: "i", ligature: "", icon: "" }
answersObjectIf the type is prompt the object keys will display to the user and the value will be returned in the promise. It defaults to { Yes: true, No: false } (Note: to include special characters like space, -, _, etc use quotation marks: "my key":
callbackFunctionThis function will be called when the notification has been dismissed or the timeout has finished.

You may additionally overwrite the following plugin settings on a notification by notification basis by adding them on the status object.

  • canTimeout
  • canPause
  • defaultTitle
  • duration - The time the notification is displayed for in milliseconds regardless of its type. (this cannot be updated later)
  • theme
  • hideProgressbar
  • transition
  • iconEnabled
  • draggable
  • dragThreshold
  • orderLatest

You may alternatively pass in an http error response like:

fetch().then().catch(error => this.$vToastify.error(error));

Only this.$vToastify.error() will look for status and statusText on the error object.

Every notification method returns a unique id associated to your notification object.

Additional methods

The notification supports multiple modes

You can either pass the mode property on the status object which is one of the following strings: "prompt", "loader" or by calling:

this.$vToastify.loader("Please Wait...")
this.$vToastify.prompt({
    body: "Are there hot singles in your area?",
    answers: { Yes: true, No: false }
})

The prompt does not return an id instead it returns a Promise so may use it as:

...}).then(value => {
    if (value) {
        this.$vToastify.prompt("Is it a scam?")
            .then(value => console.log(value ? "Yay!" : "Nay"))
    }
})

The answers object consist of a key value pairs in the object where the key is displayed to the user and the value returned by the promise. If not set it defaults to: { Yes: true, No: false }.

There are various events are emitted by the notification:

  • vtFinished
  • vtDismissed
  • vtStarted
  • vtPaused
  • vtResumed
  • vtDragStarted
  • vtBeingDragged
  • vtDragFinished

    to which you can listen by either the listen or the listenOnce method. The event's payload is an object containing the notification's id:

this.$vToastify.listen("vtDismissed", payload => console.log(payload.id))

The drag events will also include a property called position which is an object of { x: Integer, y: Integer } where x is left and y is top offset in pixels from the client view port.

Miscellaous methods:

A loader cannot be dismissed, you'll have to stop the loader yourself like so:

this.$vToastify.stopLoader(id)

This will stops the loader with the given id or loaders if array of ids given. If no id provided, all loaders will be closed. It will return the count of the loaders stopped.

For returning a notification object use:

this.$vToastify.getToast(id)

This if found returns the notification object from the visible ones or queued toasts otherwise all of the notification objects in an array from both the visible and queued toasts. If not found returns false.

For updating the notification object during run-time use:

this.$vToastify.changeToast(id, statusObject)

This will merge the object you pass in and the existing notification. It will return true if successfully updated and false if the notification isn't found.

For removing a notification use:

this.$vToastify.removeToast(id)

This will remove the notification if the id is given otherwise it will remove all of the notifications. If id supplied and not found between the queued or currently displaying notifications, it will return false, otherwise it returns the ids of the currently visible notifications.


To pass a notification from the server, assign your notification object to window.notification before importing your scripts. On mount this will gets displayed to the user. If this notification object has a property called delay, the notification display will be delayed by the given number of milliseconds.

Customisation

Extending the functionality

You can add your own methods to the plugin like so:

Vue.use(VueToastify, {
  customNotifications: {
    clientError: {
      body: "You did it!",
      defaultTitle: false,
      icon: '<svg width="50" height="50">\n' +
              '<rect width="50" height="50" style="fill:rgb(0,0,255);" />\n' +
            '</svg> ',
      canTimeout: false
    },
    moreOfTheAbove: { ...
  }
});

If the above is defined in the customNotifications object, you can use this method like so:

this.$vToastify.clientError("this will overwrite the body", "this will add a title");

or as usual pass in an object which will merge with the predefined props.

Extending the styles

Default styles maybe overridden with !important. To add custom styles you all you have to do is follow the example in ./src/assets/toast.scss and add your custom styles. Once added rename .vt-theme-dark to .vt-theme-my-custom-name and in the settings or the status object pass the theme as theme: "my-custom-name". Include this stylesheet in the project and you're good to go.

Usage

Basic usage

In your main js file:

import VueToastify from "vue-toastify";

Vue.use(VueToastify);

Then anywhere just call:

this.$vToastify.info("Easy as that");

Vuex usage

import Vue from "vue";

const mutations = {
  updateValue(state, value) {
    state.value = value;
    Vue.$vToastify.success("Successfully updated value!");
    // OR
    this._vm.$vToastify.success("Successfully updated value!")
  }
};

JSX usage

// In your vue component's methods:
runToast(){
  // This is needed to avoid using the global `h` function, which vue complains about.
  // You'll also need `lang="jsx"` in your script tag.
  const h = this.$createElement;
  this.$vToastify.success({
    body: h("div", {}, [
      h("h1", {}, "Hello"),
      h("p", {}, "World")
    ])
  });
  // OR
  const h = this.$createElement;
  this.$vToastify.success({
    body: <div>
      <h1>Hello</h1>
      <p>World</p>
    </div>
  });
  // OR With Vue 2.7
  // Your mileage with this may vary - you might need to import `h` from vue
  this.$vToastify.success(()=><div>Hello</div>)
}

You can also pass in a function for the body which will have h as an argument to circumvent the global h function.

Vue.$vToastify.success({
  body: h => h("div", {}, "hello")
});
// OR
Vue.$vToastify.success({
  body: (h) => <div>hello</div>
});
// OR as only a function
Vue.$vToastify.success((h)=><div>hello</div>);

Todos

  • Add ability to display notifications simultaneously at different locations

  • Create docs site

  • Accept components as content or as icon

  • Get url props on the answers object for redirecting on click of the button

V2

  • Clean up icons

  • Set styles as an external stylesheet

  • setSettings to return boolean.

  • url to only accept an object

  • Rewrite in Typescript (+ status object to be a class)

  • Build as TDD

Alternatives

Packages with similar capabilities:

1.9.0

5 months ago

2.0.0-alpha.2

9 months ago

2.0.0-alpha.1

1 year ago

1.8.1

2 years ago

1.8.0

4 years ago

1.7.0

4 years ago

1.6.1

4 years ago

1.6.0

4 years ago

1.5.2

4 years ago

1.5.1

4 years ago

1.5.0

4 years ago

1.4.0

4 years ago

1.3.1

4 years ago

1.3.0

4 years ago

1.2.0

4 years ago

1.1.1

4 years ago

1.1.0

4 years ago

1.0.6

4 years ago

1.0.5

4 years ago

1.0.4

4 years ago

1.0.3

4 years ago

1.0.2

4 years ago

1.0.1

4 years ago

1.0.0

4 years ago

1.0.0-alpha.2

4 years ago

1.0.0-alpha.1

4 years ago

1.0.0-alpha.0

4 years ago

0.4.5

4 years ago

0.4.4

5 years ago

0.4.3

5 years ago

0.4.2

5 years ago

0.4.1

5 years ago

0.4.0

5 years ago

0.3.0

5 years ago

0.2.1

5 years ago

0.2.0

5 years ago

0.1.1

5 years ago

0.1.0

5 years ago

0.0.9

5 years ago

0.0.8

5 years ago

0.0.7

5 years ago

0.0.6

5 years ago

0.0.5

5 years ago

0.0.4

5 years ago

0.0.3

5 years ago

0.0.2

5 years ago

0.0.1

5 years ago