Polyfills EventListener behaviours from IE11 onward
A collection of tools for website workflows.
A JavaScript wrapper for the Pod Point Network RESTful API v3 onward.
Shared code between Onward apps
The onward way to use ReBAC systems in TypeScript
Buffers a pipe until it ends. Only passes data onward if no error was emitted.
Simplify AES encryption and decryption of any JavaScript objects, implementing crypto-js library.
Singapore CPF contribution and allocation calculator (2026 rates onward)
Naturalise your inventory
Interface for gathering stats from /proc/meminfo and outputting them to STDOUT ready for onward delivery to graphite for example via sensu.
Styling for body of next content
This package was originally created as an async replacement for is-image-url. I was using that one but my sync security scanner said there was issue with one of the dependencies. I posted a pull request but a new version never got published, so onward a
A simple vue directive for debounce
Synapta interactive terminal UI — Ink-based persistent agent shell
A PouchDB plug-in that simulates CouchDB's replicator database daemon.
specialized reusable app framework for creating robot trading webapps
Simplicity WhatsApp Bot (Baileys)
FrontMCP plugins meta-package - installs all official plugins
Converts HTML documents to DOCX in the browser
Lightweight module to upload images through imgBB and other chevereto-based APIs.
The smart contracts powering blockimmo
A web server designed for running full stack, component based applications at enterprise scale.
a cheap and easy in-memory sql database that persits to S3
A JavaScript SDK implementing TPAStream's Connect Platform
A flexible LLM proxy library
j4rs stands for 'Java for Rust' and allows effortless calls to Java code, from Rust
j4rs stands for 'Java for Rust' and allows effortless calls to Java code, from Rust
A fast, flexible, configuration-based command-line interface for linting Markdown/CommonMark files
Get a lexicographic cartesian product and lexicographic permutation at any specific index from data. Generate complete lexicographic cartesian product from single or multiple set of data. Generate complete lexicographic combination from data. Generate non-lexicographic permutation and k-permutation.
Command line tool to manage WildFly containers.
Command line tool to manage WildFly containers.
plaintext double-entry accounting command line tool
Allows an item until a specified semver version, and then errors on compilation.
Pure on-chain BTC/USD price oracle algorithm
Command line tool to filter input based on a range expression
This is a fast and simple sorting algorithm which groups numbers into pairs and orders them onwards as nodes
hwloc ruby bindings for versions 1.10 onward
A simple gem that audit ActiveRecord models' attributes or methods by taking snapshots and diff them for you. Starting from scratch to work with Rails 3.2.2 onwards
FFI bindings of Assimp (Open Asset Import Library bindings) for version 4.1.0 onward
VoltRb is a gem client for VoltDB. This early release uses the JSON interface and works with VoltDB v1.1 onwards.
OpenGL core profile (3.2 onward, no deprecated functionality) bindings for Ruby 2.x. Generated from Khronos XML spec files.
Yet another FizzBuzz in Ruby! Provides simple and fast solution to a popular FizzBuzz problem for Ruby. Written in C as an example of using Ruby's C API - with the support for arbitrary large numeric values via the Bignum class, or the Integer class starting from Ruby version 2.4 onwards.
## A mirror API for Ruby In various [research][p1] [projects][p2] the advantages of having a [mirror API][p3] to separate reflection from a language implementation have been discussed, and "industry grade" implementations exist for [Java][p4] and [C#][p5]. This project aims at providing a number of specs and classes that document a mirror API for Ruby. The mirror implementation that is part of this project will use only those language facilities that are available across Ruby implementations. The specs, however, will also test behavior that cannot be provided in such a manner. The idea here is that in time, all implementations provide their own implementation of the mirror API, and all implementations collaborate on this one spec. Why do this, you ask? Because Ruby needs tools, and those tools need to be written in Ruby. If they are not, then people will be excluded from tinkering with their tools, thus impeding innovation. You only have to look at Emacs or Smalltalk to see what's possible when programmers can extend their tools, all tools, in a language they feel comfortable in. If we have a standard mirror API, all tools that are written **for** Ruby, **in** Ruby, can be shared across implementations, while at the same time allowing language implementers to use the facilities of their platform to provide optimal reflective capabilities without tying them to internals. [p1]: http://www.cs.virginia.edu/~lorenz/papers/icse03/icse2003.pdf "Pluggable Reflection: Decoupling Meta-Interface and Implementation" [p2]: http://bracha.org/newspeak-spec.pdf "Newspeak Programming Language Draft Specification, Version 0.06, pages 40 onward" [p3]: http://www.hpi.uni-potsdam.de/hirschfeld/events/past/media/100105_Bracha_2010_LinguisticReflectionViaMirrors_HPI.mp4 "Linguistic Reflection Via Mirrors" [p4]: http://bracha.org/mirrors.pdf "Mirrors: Design Principles for Meta-level Facilities of Object-Oriented Programming Languages" [p5]: http://oreilly.com/catalog/progcsharp/chapter/ch18.html "See esp. 18-3, highlighting how C# reflection works on assembly rather than VM objects"
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.