Function triggers error if argument is not array
Simple dependency graph.
Robustly get the byte length of a Typed Array
Robustly get the byte offset of a Typed Array
Robustly get the length of a Typed Array
Polyfill of future proposal for `util.parseArgs()`
Matches strings against configurable strings, globs, regular expressions, and/or functions
Like which(1) unix command. Find the first instance of an executable in the PATH.
ECMAScript extensions and shims
Check the engines and platform fields in package.json
Run an array of functions in parallel
Returns an array of all tabbable DOM nodes within a containing node.
Call an array of promise-returning functions, restricting concurrency to a specified limit.
Copy a descriptor from object A to object B
Runs a list of async tasks, passing the results of each into the next one
Yjs encoding protocols
Array manipulation, ordering, searching, summarizing, etc.
Returns true if a value is a plain object, array or function.
Runs (webpack) loaders
Parses set-cookie headers into objects
Put a bunch of emitted events in an array, for testing.
option parsing and help generation
Transform GLOB patterns to JavaScript regular expressions for fast file path matching.
Minimal async jobs utility library, with streams support
suggests Hash or Array access on error with invalid key or index
It is shortcut for Rails so if we want to have array finder which raise not found error, simply just use .find! rather than .find
Avoid all errors when accessing (deeply nested) Hash, Array or Struct keys. Safer than dig(), as will quietly return nil (or your default) if the keys requested are invalid for any reason at all. Bonus: you don't even need to fiddle with existing code. If you have already written something to access a deep key (e.g. hash[:a][:b][:c]), just surround this with '.dial' and '.call'.
error_builder provides a customizable way to format and structure error messages as arrays or hashes. It supports multiple formats, including string, array, and nested hash representations.
The valid_array gem provides to create an Array that enforces certian properties. Each element added to the array is passed to a validator function written by you. This function can raise errors, drop items or change them. vaild_array also provides compatibility with the typed-array gem. There is both 'valid_array/typed_array' which imports to `ValidArray::TypedArray` and a fully compatible 'valid-array' which passes 'valid-array's own test suite.
Features: Efficient Prime Number Identification: Utilizes optimized algorithms to quickly identify prime numbers within an array. Simple Integration: Easy to include in any Ruby project with straightforward usage. Flexible Input Handling: Supports arrays of varying sizes and integer values. Error Handling: Gracefully handles non-integer and negative values, ensuring robust performance.
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.
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)
This performs sentence proofreading using a dictionary.yml. Alternatively, by passing dictionary data in JSON format, we return an error word as an array. ex1.use yml) Jkproof.detect_words_has_error(sentence) ex2.use JSON) Jkproof.detect_words_has_error(sentence, json)
error_craft provides a customizable way to format and structure error messages as arrays or hashes. It supports multiple formats, including string, array, and nested hash representations.
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 * * NOTE: in environment.rb, specify :lib => 'exception_notifier'
EasyDownloader reduces the amount of work required to setup and check for errors when downloading from another location. This is useful when, for example, a client wants to you to pick a file up from their FTP, SFTP, or regular website on a nightly basis. EasyDownloader gives you a one-method means of downloading those files, returns with a friendly error message if it fails (geared at cron job notifications), or returns an array of file names it downloaded.