Simple update notifier to check for npm updates for cli applications
A Node.js module for sending notifications on native Mac, Windows (post and pre 8) and Linux (or Growl as fallback)
Update notifications for your CLI app
@bugsnag/js plugin to report unhandled promise rejections in React Native
webpack + node-notifier = build status system notifications
Update notifications for your CLI app, maintained in CommonJS (CJS)
Utility to create custom exceptions
@bugsnag/js plugin to capture and report uncaught exceptions
TypeScript definitions for node-notifier
TypeScript definitions for update-notifier
Core classes and utilities for Bugsnag notifiers
@bugsnag/js plugin to report unhandled exceptions in browsers
a notifier for users of fork-ts-checker-webpack-plugin
A Webpack plugin that generates OS notifications for build steps using node-notifier.
Sends out an email to the given recipient with information about an uncaught exception.
@bugsnag/js plugin to report unhandled promise rejections in browsers
Simple notifications for your website
@bugsnag/js plugin to capture and report unhandled rejections
Helpers for asserting that a JavaScript environment supports certain features necessary for the operation of the Solana JavaScript SDK
Absinthe Socket
Storybook framework-agnostic API
Push notifications in NodeJS for MacOS, Windows 7 - 11, and Linux (Growl as fallback)
list of SPDX standard license exceptions
Angular DevKit - Core Utility Library
Allows customization of: * Specify which level of notification you would like with an array of optional styles of notification (email, webhooks) * the sender address of the email * the recipient addresses * the text used to prefix the subject line * the HTTP status codes to notify for * the error classes to send emails for * alternatively, the error classes to not notify for * whether to send error emails or just render without sending anything * the HTTP status and status code that gets rendered with specific errors * the view path to the error page templates * custom errors, with custom error templates * define error layouts at application or controller level, or use the controller's own default layout, or no layout at all * get error notification for errors that occur in the console, using notifiable method * Override the gem's handling and rendering with explicit rescue statements inline. * Hooks into `git blame` output so you can get an idea of who (may) have introduced the bug * Hooks into other website services (e.g. you can send exceptions to to Switchub.com) * Can notify of errors occurring in any class/method using notifiable { method } * Can notify of errors in Rake tasks using NotifiedTask.new instead of task * Works with Hoptoad Notifier, so you can notify via SEN and/or Hoptoad for any particular errors. * Tested with Rails 2.3.x, should work with rails 2.2.x, and is apparently not yet compatible with rails 3.
Exception notification by email for Rails apps
Simple ruby implementation to send notifications to Asana when a exception happens in Rails or Rack-based apps by creating a task and uploading exception details to the task using zip archives
Rack middleware to send email when exceptions are raised
Exception File Notifier records exception logs in JSON format, helping you track errors in the production environment.
Extracted exception notifier of Lipsiadmin
a pushover notifier for exception_notification
To avoid having to update exception notifiers in all the different repositories, we pull out commonalities and wrap them into gems
This rubygem does not have a description or summary.
Plugin for integration ExceptionNotifier with DelayedJob
Allows customization of: * Specify which level of notification you would like with an array of optional styles of notification (email, webhooks) * the sender address of the email * the recipient addresses * the text used to prefix the subject line * the HTTP status codes to notify for * the error classes to send emails for * alternatively, the error classes to not notify for * whether to send error emails or just render without sending anything * the HTTP status and status code that gets rendered with specific errors * the view path to the error page templates * custom errors, with custom error templates * define error layouts at application or controller level, or use the controller's own default layout, or no layout at all * get error notification for errors that occur in the console, using notifiable method * Override the gem's handling and rendering with explicit rescue statements inline. * Hooks into `git blame` output so you can get an idea of who (may) have introduced the bug * Hooks into other website services (e.g. you can send exceptions to to Switchub.com)
Use exception_notification to send rails exceptions to graylog2.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.