Considerations
General considerations when using Better Toast.
Bundle size
A great web experience doesn't just look and move beautifully, it should load quickly, too.
If you're bundlephobic, Bundlephobia has the numbers - check minified size, gzip, and dependency graph before you commit.
Caveats
Toast enter animations use the CSS @starting-style at-rule. This feature is supported in modern evergreen browsers, with coverage continuing to improve. For up-to-date compatibility details, refer to Can I use.
In environments where the at-rule is not yet supported, toast notifications will still render correctly, but without the entrance animation.
Toaster duration and lifecycle
On the component that displays better-toaster, showing a toast in constructor or ngOnInit can happen before the duration input is bound, so the first toast may use the library's default duration until the view is ready.
To avoid that mismatch, pass durationMs in the toastOptions object when showing the toast and use the same value as your better-toaster's duration binding.
When the toast comes from a component nested further down in the same view tree, or from a service, you usually will not hit this duration-binding timing issue.