Compile JS objects into revivable JS code strings
[fork] TextEncoder and TextDecoder (Polyfill for the Encoding Living Standard's API) For Node.JS.
Polyfill for the Encoding Living Standard's API.
An implementation of the Infra Living Standard
An implementation of the URL Living Standard
A ponyfill for the ES 2015 (ES6) `Array.from()`.
A specification of HTML Living Standard for markuplint
A suite of parsers and compilers for WordPress styles.
React components style guide generator
Build an absolute URL from a base URL and a relative URL (RFC 1808). No dependencies!
Create a duplex stream from a writable and a readable
A modern DOM implementation
Slider component for React
Haraka plugin that saves logs to Elasticsearch
ES Object-related atoms: Object, ToObject, RequireObjectCoercible
string representations of objects in node and the browser
A tiny vanilla javascript form validation library
Swagger UI Express
A fast, safe, compliant XML parser for Node.js and browsers.
An Object.keys replacement, in case Object.keys is not available. From https://github.com/es-shims/es5-shim
Is this value a JS Date object? This module works cross-realm/iframe, and despite ES6 @@toStringTag.
Is this value a JS Number object? This module works cross-realm/iframe, and despite ES6 @@toStringTag.
Local Markdown documentation hub with a built-in MCP server — coding agents create ADRs, draw diagrams and detect drift while you code.
Is this value a JS Boolean? This module works cross-realm/iframe, and despite ES6 @@toStringTag.
Auto-syncs records in client-side JS (through a Model DSL) from changes (updates/destroy) in the backend Rails server through ActionCable. Also supports streaming newly created records to client-side JS. Supports lost connection restreaming for both new records (create), and record-changes (updates/destroy). Auto-updates DOM elements mapped to a record attribute, from changes (updates/destroy).
A tool to help track down the source of an object leak in a Ruby process
A memory profiler focusing on long-lived objects.
Debugging live Ruby objects with control+c
A container for storing objects and values in the application as long as the request lives. Registry implements ruby's Singleton module, the same object is always available throughout your application.
With minimal set up ActiveSync presents limited rails model interfaces within the JS font end. Records accessed are kept updated through action cable.
Nested OpenStruct optimized for short-lived objects.
This module allows you to create a connection to Ableton Live 8.1.x through a Max4Live plugin. You can then manipulate objects in the LOM (Live Object Model) as though they were Ruby objects.
Easily patch objects in a Rails app with live-reload support.
has_alter_ego makes it possible to keep seed and live data transparently in parallel. In contrast to other seed data approaches has_alter_ego synchronizes the seed definitions with your database objects automagically unless you've overridden it in the database.
LionAttr uses Redis to store Mongoid object in-mem giving it fast accessibility. It also gives convenience to manipulate numeric attributes which will be called live attrbutes. With live attributes, you can increase, decrease database for high performance.
Transaction::Simple provides a generic way to add active transaction support to objects. The transaction methods added by this module will work with most objects, excluding those that cannot be Marshal-ed (bindings, procedure objects, IO instances, or singleton objects). The transactions supported by Transaction::Simple are not associated with any sort of data store. They are "live" transactions occurring in memory on the object itself. This is to allow "test" changes to be made to an object before making the changes permanent. Transaction::Simple can handle an "infinite" number of transaction levels (limited only by memory). If I open two transactions, commit the second, but abort the first, the object will revert to the original version. Transaction::Simple supports "named" transactions, so that multiple levels of transactions can be committed, aborted, or rewound by referring to the appropriate name of the transaction. Names may be any object except nil. Transaction groups are also supported. A transaction group is an object wrapper that manages a group of objects as if they were a single object for the purpose of transaction management. All transactions for this group of objects should be performed against the transaction group object, not against individual objects in the group. Version 1.4.0 of Transaction::Simple adds a new post-rewind hook so that complex graph objects of the type in tests/tc_broken_graph.rb can correct themselves. Version 1.4.0.1 just fixes a simple bug with #transaction method handling during the deprecation warning. Version 1.4.0.2 is a small update for people who use Transaction::Simple in bundler (adding lib/transaction-simple.rb) and other scenarios where having Hoe as a runtime dependency (a bug fixed in Hoe several years ago, but not visible in Transaction::Simple because it has not needed a re-release). All of the files internally have also been marked as UTF-8, ensuring full Ruby 1.9 compatibility.