- Toast Component Injection without being passed
ViewContainerRef
- No use of
*ngFor
. Fewer dirty checks and higher performance. - AoT compilation and lazy loading compatible
- Component inheritance for custom toasts
- SystemJS/UMD rollup bundle
- Animations using Angular's Web Animations API (polyfill needed for older devices)
- Output toasts to a target directive
npm install ngx-toastr --save
@angular/animations
package is a required dependency for the default toast
npm install @angular/animations --save
step 1: add css
- copy toast css to your project.
- If you are using sass you can import the css.
@import 'node_modules/ngx-toastr/toastr';
- If you are using angular-cli you can add it to your angular-cli.json
"styles": [
"styles.scss",
"node_modules/ngx-toastr/toastr.css"
]
step 2: add ToastrModule to app NgModule
import { CommonModule } from '@angular/common';
// BrowserAnimationsModule is required
import { BrowserAnimationsModule } from '@angular/platform-browser/animations';
import { ToastrModule } from 'ngx-toastr';
@NgModule({
imports: [
CommonModule,
BrowserAnimationsModule,
ToastrModule.forRoot(), // ToastrModule added
],
bootstrap: [App],
declarations: [App],
})
class MainModule {}
Success:
import { ToastrService } from 'ngx-toastr';
@Component({
...
})
export class YourComponent {
constructor(private toastrService: ToastrService) {}
showSuccess() {
this.toastrService.success('Hello world!', 'Toastr fun!');
}
}
There's global options and individual toast options. All individual toast options are included in the global options. See file toastr-config.ts
The toastComponent can be inherited and modified. See the pink toast in the demo. It has a different animation and inline style.
maxOpened: number = 0; // max toasts opened. Toasts will be queued
autoDismiss: boolean = false; // dismiss current toast when max is reached
iconClasses = { // classes used on toastr service methods
error: 'toast-error',
info: 'toast-info',
success: 'toast-success',
warning: 'toast-warning',
};
newestOnTop: boolean = true; // new toast placement
preventDuplicates: boolean = false; // block duplicate messages
toastComponent = Toast; // the Angular component that will be used
closeButton: boolean = false; // show close button
timeOut: number = 5000; // time to live
enableHtml: boolean = false; // allow html in message. (UNSAFE)
extendedTimeOut: number = 1000; // time to close after a user hovers over toast
progressBar: boolean = false; // show progress bar
toastClass: string = 'toast'; // class on toast
positionClass: string = 'toast-top-right'; // class on toast
titleClass: string = 'toast-title'; // class inside toast on title
messageClass: string = 'toast-message'; // class inside toast on message
tapToDismiss: boolean = true; // close on click
onActivateTick: boolean = false; // fire ApplicationRef.tick() from the toast component when activated. Helps show toast from a websocket event
NEW FOR VERSION > 3 Option 1: Pass values to ToastrModule.forRoot
// your NgModule
imports: [
ToastrModule.forRoot({timeOut: 0}),
],
Option 2: Inject ToastrConfig, typically in your root component, and customize the values.
import { ToastrConfig } from 'ngx-toastr';
import { Component } from '@angular/core';
@Component({
selector: 'app-root',
templateUrl: './app.component.html',
styleUrls: ['./app.component.css']
})
export class AppComponent {
constructor(toastrConfig: ToastrConfig) {
toastrConfig.timeOut = 100;
}
}
success, error, info, warning take (message, title, ToastConfig)
pass a ToastConfig object to replace several default settings.
// OPTIONAL: import the ToastConfig interface
import { ToastConfig } from 'ngx-toastr';
const errorConfig: ToastConfig = {timeOut: 10000};
this.toastrService.error('everything is broken', 'title is optional', errorConfig);
export interface ActiveToast {
toastId: number; // Your Toast ID. Use this to close it individually
message: string; // the message of your toast. Stored for prevent duplicate reasons
portal?: any; // a reference to the component see portal.ts
toastRef?: ToastRef<any>; // a reference to your toast
onShown?: Observable<any>; // triggered when toast is active
onHidden?: Observable<any>; // triggered when toast is destroyed
onTap?: Observable<any>; // triggered on click
onAction?: Observable<any>; // available for your use in custom toast
}
Toastr Service will return undefined if prevent duplicates is on.
Put toasts in a specific div inside your application. This should probably be somewhere that doesn't get deleted.
Add ToastContainerModule.forRoot()
to ngModule after the ToastrModule.forRoot()
Add a div with toastContainer
directive on it.
import { ToastContainerDirective } from 'ngx-toastr';
@Component({
selector: 'app-root',
template: `<div toastContainer class="toast-top-right"></div>`,
})
export class AppComponent implements OnInit {
@ViewChild(ToastContainerDirective) toastContainer: ToastContainerDirective;
constructor(private toastrService: ToastrService) {}
ngOnInit() {
this.toastrService.overlayContainer = this.toastContainer;
this.toastrService.success('in div');
}
}
If you are using SystemJS, you should also adjust your configuration to point to the UMD bundle.
In your systemjs config file, map
needs to tell the System loader where to look for ngx-toastr
:
map: {
'ngx-toastr': 'node_modules/ngx-toastr/toastr.umd.js',
}
toastr original toastr
angular-toastr AngularJS toastr
notyf notyf (css)
MIT