TypeScript definitions for boom
Boom response objects in Express
Fastify Boom support - HTTP-friendly error objects
TypeScript definitions for express-boom
Extremely fast utf8 only stream implementation
A gRPC implementation of the awesome Boom library to help create gRPC-friendly error objects.
A decorator around Boom (HTTP-friendly error objects) to empower it
HTTP-friendly error objects
Decorates a Hapi server's reply interface with functions to make it easy to reply with Boom errors
Boom error wrapper
Simply create sub-classed Boom errors for Hapi applications.
boom meeting
HTTP-friendly error objects. Fork from boom
Boom response objects in Express
A utility to convert Objection database errors into Boom HTTP errors
Using boom inside koa context
Boom external js sdk
Structure Boom errors into a more desirable format
A customizable React confetti explosion component for celebrations and special events
Rest client that goes :boom:
Simple error objects in node. Created specifically to be used with the fetchr library and based on hapi.js' Boom.
Boom js with Types matching HTTP status codes
Response timeout middleware for Koa and Lad (uses Boom by default)
Wraps errors in micro with Boom
An attempt at a game engine. Not usable atm.
todo-or-boom, a todos and fixme linter.
An attempt at a game engine. The build dependency. Not usable atm.
test crate
This crate provides utilities for exiting processes on errors gracefully.
Unchecked assertions of unreachability which panics on debug builds.
deserialize env vars into typesafe structs
A commercial window cleaning cost calculation engine for facility managers in Northern Ontario. Built by Binx Professional Cleaning.
DEPRECATED. Use crossbeam-channel instead.
Sources doctests from dedicated files into Rustdoc documentation while hiding select lines
Quality of life utilities for error handling in Rust.
rustc hates him! Sidestep borrow checking with this weird trick (no unsafe inside).
God it's about every day where I think to myself, gadzooks, I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if I had something like boom to store all these commonly-used text snippets for me? Then I realized that was a worthless idea since boom hadn't been created yet and I had no idea what that statement meant. At some point I found the code for boom in a dark alleyway and released it under my own name because I wanted to look smart.
boom - maintain your OS X desktop. Use boom so that your desktop only contains files and folders for the current project you are working on.
Create ruby server or integrates with a Rails app to integrate NATS messages consumer
The .gitlab-ci.yml is hard to maintain if your project grows, and its hard to determine what is defined where, and why. This Ruby DSL allows you to not be limited by YAMLs limitations, but have all Ruby's features at your disposal.
boom
My Implementation of @holman's boom [https://github.com/holman/boom/]
Software management system.
Provides an interface to REST apis with objects and a cache. Zero effort!
Zap is a simple command line key-value store. There are no collections, just a single namespace, and only three letters in the command. ZAP!
Peanut is a simple command line clipboard manager similar to BOOM. We use key/value stores instead of lists, keeping things simple.
Convert google maps to ascii for great fun! :zap: :boom: :heart:
Supports the Boomi REST Webservice
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.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.