Command runner
A shim for the setImmediate efficient script yielding API
loop through commands in fun and amazing ways!
High-priority task queue for Node.js and browsers
JavaScript Performance Monitor
High-priority task queue for Node.js and browsers
Exposes stats about the libuv default loop
Run a list of functions in order in a given object context. The functions can be callback-taking or promise-returning.
fast, tiny `queueMicrotask` shim for modern engines
C function to get the current libuv event loop for N-API
Polyfill for perf_hooks.monitorEventLoopDelay(...)
Measure event loop lag
Tiny helper to prevent blocking Node.js event loop
Middleware for the middy framework that allows to easily disable the wait for empty event loop in a Lambda function
Sequence your effects naturally and purely by returning them from your reducers.
Offload tasks to a pool of workers on node.js and in the browser
A JavaScript text diff implementation.
Node-RED nodes to help flow looping.
Inquirer rawlist prompt
Governed AI coding harness for pi.dev — bootstrap, plan, execute, review, and steer with deterministic policy gates
Node-RED nodes to looping (fixed steps, condition based or iterating over arrays, objects, maps, sets, string).
Create an animated loop of a list of text for your headings
Zero CPU overhead, zero dependency, true event-loop blocking sleep
Small agentic loop
Write a short summary, because RubyGems requires one.
Interactive Ruby command-line tool for REPL (Read Eval Print Loop).
The idea here is to take arguments off of a stack, run a command, and proceed down the stack iff the command exits 0. Why? Consider running rspec with a tight focus, adding breadth on success
nom is a command line tool that helps you lose weight by tracking your energy intake and creating a negative feedback loop. It's inspired by John Walker's "The Hacker's Diet" and tries to automate things as much as possible.
cliblog is a command-line blog client. It loops waiting for command-line input, and if 'edit' or 'create' command is input, then it will launch user's favorite EDITOR brought from ENV variable. Or you can input your editor's path manually if ENV['EDITOR'] is not set. As for me, I'm using 'vim' for my personal typo-powered blog.
Carrousel is a robust utility designed to take a list of generic items, and given some command, perform that command on each item in that list. Depending on the commands return value, Carrousel will track which items have been completed successfully, and retry items as necessary. It will save your progress in a status database and you can quit the loop and come back later to finish unprocessed items.
I don't want a single thing preventing me from starting off (even the smallest) library without a good infrastructure to support TDD and clean coding standards. I got tired of reconfiguring the same tools in basically the same way every time. With this one command you can set up a library, fire up Guard, and jump right into the TDD loop: Red, Green, Refactor.
* Pure Ruby library for creating desktop-like interfaces in the command line. * Flexible and easy to use utilities for focus/actions/scroll/events/cursor. * Support high level APIs similar to HTML DOM APIs like layouts, styles, box-model, cascade styles, XML/ERB, boxes, fonts, images, colors, easing, * Low level utilities can be used independently without bloating the performance * Event loop supporting set_timeout, wait_for, set_interval * Many high level widgets, utilities implemented expected in GUIs. * WIP (my first Ruby project)
pikuri-code adds the shell-and-dev-loop layer on top of pikuri-workspace's filesystem tools: a +Pikuri::Code::Bash+ that runs commands via the +Pikuri::Subprocess+ chokepoint with +Confirmer+ gating (optionally wrapped in a +Pikuri::Code::Bash::Sandbox::Bubblewrap+ filesystem sandbox), plus the demo +bin/pikuri-code+ binary that wires file + shell + web tools into an interactive coding agent rooted at the current working directory. The +Pikuri.prompt+ search path picks up this gem's +prompts/coding-system-prompt.txt+ automatically on require.
RCrewAI is a powerful Ruby framework for creating autonomous AI agent crews that collaborate to solve complex tasks. Build intelligent workflows with reasoning agents, tool usage, memory systems, and human oversight. Key Features: • Multi-Agent Orchestration: Create crews of specialized AI agents that work together • Multi-LLM Support: OpenAI GPT-4, Anthropic Claude, Google Gemini, Azure OpenAI, Ollama • Rich Tool Ecosystem: Web search, file operations, SQL databases, email, code execution, PDF processing • Agent Memory: Short-term and long-term memory for learning from past executions • Human-in-the-Loop: Interactive approval workflows and collaborative decision making • Advanced Task Management: Dependencies, retries, async execution, and context sharing • Hierarchical Teams: Manager agents that coordinate and delegate to specialist agents • Production Ready: Security controls, error handling, comprehensive logging, and monitoring • Ruby-First Design: Built specifically for Ruby developers with idiomatic patterns • CLI Tools: Command-line interface for creating and managing AI crews
Crowdfund is a Ruby program developed based on Pragmatic Studio's Ruby Programming hands-on video course, and distributed as a Ruby gem. This program has been developed using all the strengths of Ruby including the following. Ruby Programming Environment * Installing Ruby on your favorite operating system (free exercise) * Running Ruby using the interactive Ruby shell (irb) and writing Ruby program files * Using Ruby's documentation system to get help * Installing external Ruby libraries using RubyGems * Troubleshooting common problems Ruby Language Constructs * Expressions and variables * Numbers, string, and symbols (free video & exercise) * Loops and conditional expressions * Arrays and hashes (free video & exercise on hashes) * Classes, modules, and structs Object-Oriented Programming * Using built-in Ruby classes * Defining your own classes with state and behavior (free video & exercise) * Creating unique objects * Telling objects what to do by calling methods * Modeling class-level inheritance relationships * Sharing code with mixins Object-Oriented Design Principles * Encapsulation * Separation of concerns * Polymorphism * Don't Repeat Yourself * Tell, Don't Ask Blocks and Iterators * Calling built-in methods that take blocks * Writing your own methods that yield to blocks * Implementing custom iterators * Effectively using blocks in your programs Organizing Ruby Code * Creating a Ruby project structure * Separating source files for easier reuse and testing * Namespacing to avoid naming clashes * Input/Output * Reading data from files * Writing data to files * Creating an interactive console prompt * Handling command-line input Unit Testing * Writing and running unit tests with RSpec * Test-driven development and the red-green-refactor cycle * Stubbing methods to control tests * Refactoring code, safely! Distribution * Conforming to RubyGems conventions * Writing a GemSpec * Building a RubyGem * Publishing a RubyGem to a public server Ruby Programming Idioms
* http://rubysideshow.rubyforge.org/irb_callbacks == DESCRIPTION: This gem adds callbacks to irb, intended for you to override at your discretion. == FEATURES: irb's control flow looks like this: loop: * prompt * eval * output This gem adds three callbacks to each phase. module IRB: * self.before_prompt * self.around_prompt (call yield) * self.after_prompt * self.before_eval * self.around_eval (call yield) * self.after_eval * self.before_output * self.around_output (call yield) * self.after_output == SYNOPSIS: # Here's my ~/.irbrc file (which is run at irb startup) require 'rubygems' require 'irb_callbacks' require 'benchmark' # This little snippet will time each command run via the console. module IRB def self.around_eval(&block) @timing = Benchmark.realtime do block.call end end def self.after_output puts "=> #{'%.3f' % @timing} seconds" end end # And a sample irb session: $ irb irb(main):001:0> 1_000_000.times { |x| x + 1 } => 1000000 => 0.330 seconds == CAVEATS: The three around_* callbacks all require you to call the block that's passed in. If you don't do it, undefined behavior may occur. == INSTALL: * sudo gem install irb_callbacks == LICENSE: (The MIT License) Copyright (c) 2008 Mike Judge Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
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.