Why build your own notifications?
On a few projects now I've had to "reinvent the wheel" of system notifications. This is primarily a result of being unable to style the basic JavaScript alert() function and being extremely limited in what alert() and confirm() can do.
So I thought to myself, why not a really easy notification system that you can plug into any web app. Yes, React-Alerts and many other projects exist. But, all of those you still have to think about implementation and still have to write code.
In my case, there's no code. You can interact with it without ever writing actual notification code. It is my, possibly unpopular opinion, that notifications should be standalone code and should have a simple interface to interact with from anywhere. It really shouldn't matter what component or what API generates an error/notification, it should simply display. I believe this contributes to anti-fragility because when something goes terribly wrong, the last thing you want is for your error notifications to stop working.
How does it work?
Good question! Somewhere in your app, include the CSS+script tag: Note the default_timeout and initial_delay arguments. Much of the settings can be applied right in the script tag and never thought about again.
How do you interact with it?
Another good question! When the page is initially loaded you can set initial messages (generated on the server during load) with:
Then dynamically when API calls are made you can do: