Fluent, composable, type-safe error matching and recovery for promises
Allow parsing of optional catch bindings
`Start a promise chain
Compile optional catch bindings
Chain functions, generators, Node streams, and Web streams into a pipeline with backpressure support.
HANDLE CONFIGURATION ONCE AND FOR ALL
chdir in chainer fashion + read file
A utility for managing a prototype chain
API for combining call site modifiers
TypeScript definitions for stream-chain
A small opinionated library to bring Rust-like results idiomatically to TypeScript.
A simple asynchronous tool
The Aikido Safe Chain wraps around the [npm cli](https://github.com/npm/cli), [npx](https://github.com/npm/cli/blob/latest/docs/content/commands/npx.md), [yarn](https://yarnpkg.com/), [pnpm](https://pnpm.io/), [pnpx](https://pnpm.io/cli/dlx), [rush](https
Tap into a promise chain without affecting its value or state
An extendable Error class that actually works, with TypeScript definition files, supporting old and new style classes and compatibility even with the oldest browsers
Light client that connects to Polkadot and Substrate-based blockchains
[![NPM version][npm-image]][npm-url] [![NPM downloads][npm-downloads]][npm-url] [![CI Status][ci-image]][ci-url]
Node.js implementation of a proxy server (think Squid) with support for SSL, authentication, upstream proxy chaining, and protocol tunneling.
Chain Registry types
Old abstractions from LangChain.js
Gracefully handle a Promise using async/await.
Promise and RxJS wrappers around the Polkadot JS RPC
NodeJS Require that let you handle module not found error without try/catch
Defines a CAIP-25 based endowment permission and helpers for interfacing with it
The plugin is really rather simple; here's the ignore_nil method: def ignore_nil(&block) begin yield rescue NoMethodError, RuntimeError => e if (e.message =~ /You have a nil object when you didn't expect it/) || (e.message =~ /undefined method `.*?' for nil:NilClass/) || (e.message =~ /^Called id for nil/) return nil else raise e end end end What's interesting about this is it catches both NoMethodError and RuntimeError, both of which can occur if a method unexpectedly returned nil and you called a method on it, but *ONLY* if the error message matches! This means legitimate NoMethodError and RuntimeError messages will not be bothered by ignore_nil, and will still raise in your application as you expect. I've used this in a production application since about mid/late 2008, I'd consider it very stable. Feedback welcome!
ignore_nil lets you happily ignore nil methods on long method chains. Keeps code pretty and much safer than "rescue nil", since it only catches NoMethodError on nil objects
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.