v1.2.0

🚀 New features

• Full Nuxt support: Install Vue Toastification as a Nuxt module without hassle. docs (#47) (d88d9bd), closes #46

v1.1.1

🔧 Bug fixes

• Typescript support was broken: Path aliases broke module resolution on declaration files. (#45) (6ddb7d7), closes #44

v1.1.0

🧪 Tests

• 100% Test coverage! Every single line is thoroughly tested to guarantee maximum reliability (#42) (090186e), closes #41

🚀 New features

• Added onMounted plugin option: Makes it easy to grab the generated container vue instance. docs (#42) (c055798), closes #38

🔧 Bug fixes

• hasProp only worked with objects: Now hasProp works with any component type. (#42) (c92794a), closes #40
• False negatives on isToastContent: Fixed isToastContent to identify more Vue component types. (#42)(c92794a), closes #39
• .update() may break: Fixed issue with .update() trying to create toasts without content. (#42)(c055798), closes #37

📖 Documentation

• Added recommended way to get position and type constants: It is now recommended to use the constants POSITION.TOP_RIGHT and TYPE.SUCCESS, etc, instead of the string equivalents "top-right", "success". Import it as named imports from "vue-toastification".

v1.0.0

⚠️ Breaking changes

• hideCloseButton removed! Now set closeButton: false to hide it. (#35) (ea1a448)
• Custom icon object shape changed! Previous shape { tag, children, class } conflicts with JSX, so it was changed to { iconTag, iconChildren, iconClass } (#35) (ea1a448)
• Renamed examples folder to public! Examples did not make sense since it was the code for the demo. (#35) (eb56db2)
• Namespaced components with Vt prefix! Some editors were picking up internal components by name. (#35) (4158311) closes #32

🚀 New features

• Full typescript support: Entirely rewritten in Typescript (#35) (eb56db2), closes #36
• Added containerClassName plugin option: Now custom classes can be added to containers docs (#35) (58c1d3e)

🔧 Bug fixes

• Added Plugin options declaration to types: PluginOptions was missing from the module declaration. #34 (03cd140)
• Dynamic container element updates: $updateDefaults({ container: yourHTMLElement } ) was not updating the container component, but now does without losing any state or affecting UI. (#35)(6428344) Thanks to @tomeus

📖 Documentation

• Added onClose documentation: onClose documentation was missing, even though it was implemented. docs #35 (eb56db2)

📦 Bundle

• Switch from webpack to rollup: Smaller and more diverse builds with support for tree shaking.

v0.9.0

🚀 New features

• Show close button on hover: Close buttons can now be hidden and shown when hovering the toast. #1 (resolved by #33) docs

v0.8.0

🚀 New features

• Icon custom components: Custom components can now be used as icons. #29 (resolved by #31) docs
• Close button custom components: Custom components can now be used as close buttons. #30 (resolved by #31) docs
• Close button custom classes: Close buttons now accept custom classes. #30 (resolved by #31) docs

v0.7.0

🔧 Bug fixes

• Critical toast options bug: Toasts created with types ignored custom options #28 (a031b79)

v0.6.5

🚀 New features

• Custom component body classes: Custom toast body classes are now also applied to a wrapper component when using custom components. docs (40b3ae6)

🔧 Bug fixes

• Safari toast sizes: Toasts with default icons in Safari appeared bigger than they should be #27 (resolved by 07e159f and #25)
• Inconsistent icon's height: Icon's height would change if using custom components due to flexbox (40b3ae6)

📦Bundle

• Unused deps: Cleaned unused dependencies
• 10% reduction in size: 10% reduction in bundle size by centralizing prop definitions and by removing polyfills for array and object destructuring.

v0.6.0

🚀 New features

• Ligature Icons: Icons now support ligatures docs (#23)

v0.5.2

🔧 Bug fixes

• Function-based custom components: Nested function-based components were not being taken into account (#21)