Stream transform passthrough that calls a function.
Runtime to be use with the Flow Enums transform.
simplified stream construction
simplified stream construction
Allow parsing of the flow syntax
Welcome to the README of Gurx, an typescript-native reactive state management library for complex web applications and components that do not have the symmetry of the store object and the component tree.
A JavaScript parser built from the Hermes engine
Strip flow type annotations from your output code.
Create atom (⚛) representation for your application, packages and libraries
Babel preset for all Flow plugins.
Flow types for the Flow-ESTree spec produced by the hermes parser
JavaScript parser written in OCaml. Produces ESTree AST
Babel transform for Flow Enums.
Flow types for the Javascript AST
A repository of high quality flow type definitions
Microsoft Authentication Library for js
Octokit authentication strategy for OAuth clients
GitHub OAuth App authentication for JavaScript
Flowtype linting rules for ESLint.
[](https://www.npmjs.com/package/@virtuoso.dev/gurx) [](https://www.npmjs.com/package/@virtuoso.dev/gurx) [ flow through the network, and fruiting bodies (creative breakthroughs) emerge at the surface.
Do you forget to update a story card on Mingle when the card has moved into developers' hands? How about forgetting to update the story card to kick-off its sign off process when story is completed? If we let these sloppiness happen too often, communication flow will be hindered, and the time it takes to provide business value through story completions will be lengthened. Fortunately, Minglr can help.
Time-bound cognitive resource model for brain-modeled agentic AI — sand grains flow through a narrowed neck, depleting attention resources until the hourglass is flipped to renew the cycle
A metadata backend that lets Active Storage store its Blob, Attachment, and VariantRecord rows in Amazon DynamoDB (through the aws-record gem) instead of Active Record. Blob bytes still flow through any Active Storage Service (Disk, S3, ...); only the metadata lives in DynamoDB. Implements the generic custom Active Storage backend contract.
QA Robusta is an automation framework easing pain points away from automation test case writers. How is pain relieved? * Elements, such as links, buttons, and other html objects are defined in one location. This ensures over time the user won't have definitions spread out throughout different layers of code requiring time consuming updates if the application under test is modified. * Well defined flows allows the user to have a common means for navigating and controlling interactions with the application under test. This takes all logic out of test classes and yields in higher more modular code re-use. * When an application requiring testing has the elements and flows implemented less code savy resources can easily add new test cases once trained on how to access the flows and elements. * When ever a link or button is clicked a screen shot is taken * Results are available under site/results directory in html format. Report includes the rdoc on a per test class method along with any screen shots taken. Example report: https://cyberconnect.biz/opensource/demo_results.html * Transparent remote Unix command execution leading to well defined interfaces for common task. For example, one may have a class defined specifically for RemoteUnixNetwork. This class would have methods such as, assign_ip, ifup, ifdown, etc. This class then would be able to perform these task on any remote Unix machine. * Executes the same on Windows or Linux/Unix environments. Developers have the freedom to develop on the platform of choice. * Mechanize extension: Allows the user to define a web application's page elements in a YAML format and provide navigation paths accessing the YAML structure to interact with the web application. Users can also perform direct http.post or any other mechanize functionality when defining state-full interfaces to hit a web application without going through a browser.
pikuri-vectordb gives a pikuri-core agent a +vectordb_search+ tool over a local document corpus — agentic search, the agent decides when to retrieve. Ships a swappable backend (a pure-Ruby +Backend::InMemory+ for teaching and a thin +Backend::Chroma+ HTTP client for persistence), a chunker, an embedder wrapper over +RubyLLM.embed+, and an optional +Reranker::LlamaServer+ that speaks +/v1/rerank+ against a cross-encoder model. Text extraction goes through +Pikuri::FileType.read_as_text+ in pikuri-core, which handles plain text / Markdown / PDF; HTML extraction is a deferred follow-up. Hosts wire the feature via +c.add_extension Pikuri::VectorDb::Extension.new(...)+ inside the +Agent.new+ block — same opt-in shape as +pikuri-tasks+ / +pikuri-skills+. The bundled +Pikuri::VectorDb::LIBRARIAN+ persona is the privilege-separated sub-agent counterpart for hosts that want recall to flow through a child rather than the parent's context. Three model endpoints in the full setup — chat (via ruby_llm), an embedder (via +RubyLLM.embed+), and an optional reranker (HTTP +/v1/rerank+). A single +llama-server+ in router mode serves all three by default, loading each cached GGUF on demand; see the gem's README for details.
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.