Convert JsonSchema based document into structured and simplified data tree
mdast extension to parse and serialize MDX or MDX.js JSX
mdast extension to parse and serialize GFM footnotes
mdast extension to parse and serialize MDX (or MDX.js) expressions
mdast extension to parse and serialize GFM strikethrough
mdast extension to parse and serialize GFM task list items
mdast extension to parse and serialize MDX.js ESM (import/exports)
mdast extension to parse and serialize GFM tables
A helper library for loading and saving the .api.json files created by API Extractor
mdast extension to parse and serialize math
mdast extension to parse and serialize frontmatter (YAML, TOML, etc)
Node.js API (Node-API)
Types and validators that help describe the model of a Backstage Catalog
TypeScript client library for the Mistral AI API
Detect NSFW content client-side
Finite State Machines and Statecharts for the Modern Web.
Regular Expressions parser in JavaScript
Tensorflow model converter for javascript
The official TypeScript library for the OpenAI API
mdast utility to serialize markdown
unist utility to recursively walk over nodes, with ancestral information
mdast utility to transform to hast
unist utility to visit nodes
Microsoft Azure Storage SDK for JavaScript - Blob
RubyTree is a Ruby implementation of the generic tree data structure. It provides simple APIs to store named nodes, and to access, modify, and traverse the tree. The data model is node-centric, where nodes in the tree are the primary structural elements. It supports all common tree-traversal methods (pre-order, post-order, and breadth first). RubyTree mixes in the Enumerable and Comparable modules and behaves like a standard Ruby collection (iteration, comparison, etc.). RubyTree also includes a binary tree implementation, which provides in-order node traversal besides the other methods. RubyTree can import from and export to JSON, and supports Ruby’s object marshaling.
A comprehensive Ruby tool for building and optimizing documentation for Large Language Models. Features include: generating llms.txt files from documentation directories with automatic file prioritization, transforming individual markdown files by expanding relative links to absolute URLs, bulk transforming entire documentation trees with customizable exclusion patterns, comparing content sizes to measure context window savings, and serving LLM-optimized documentation. Provides both CLI and Ruby API with configuration file support.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.