> Boots a Live app.
A plug-and-play React component for capturing live Core Web Vitals and diagnostic metrics directly inside any application.
ubia web live core
mars-cli-live core
A generic toolkit to help with accessibility
P2P CDN Live core functionality
Modular Prisma Studio components
Javascript audio library for the modern web.
Predictable state container for JavaScript apps
High-performance image processing library for native use and the web
Development server for Rspack
React Sigma - Layout core
> [!WARNING] > This package is not meant to be used directly, it's a shared dependency of `sanity/presentation` and `@sanity/visual-editing`. Using it in production is at your own risk.
Is this specifier a node.js core module?
Babel compiler core.
Minimal lightweight logging for JavaScript, adding reliable log level methods to any available console.log methods
core-js compat
Core components for creating a txwrapper lib.
Standard library
An Observable Object
[](https://www.npmjs.com/package/jsdoc-type-pratt-parser) []
Reactive dataflow processing.
HTML5 Medical Image Viewer Component
Core functions & classes shared by multiple AWS SDK clients.
Parses raw events from the Formula1.com live timing stream
Dump C level and Ruby level backtrace from living process or core file using gdb.
Rails-AI-Bridge introspects your Rails application and exposes structure to AI assistants via static context files and a live Model Context Protocol (MCP) server. It classifies Active Record models semantically (Core, Join, Supporting), optionally surfaces non-ActiveRecord Ruby classes under app/models (tagged POJO/Service), and integrates with editors and assistants such as Claude, Gemini, Cursor, and Windsurf.
pikuri-core is the lean, audit-friendly foundation of the pikuri family: Pikuri::Agent (a thin wrapper around ruby_llm's chat loop) with its Configurator + Extension protocol, the strict Pikuri::Tool framework, a listener surface for rendering / budgets / sub-agents, and four bundled stateless tools (calculator, web search, web scrape, fetch). Extensions (skills, MCP, workspace, coding stack, named-agent personas) live in sibling gems so a privacy-conscious user can install just this core and audit a minimal dependency tree. For the convenience bundle that pulls in everything, see the +pikuri+ metagem.
Engram gives AI agents durable, long-term memory. It recalls relevant facts about a user and injects them into the prompt, so an agent appears to remember across sessions. Framework-agnostic core with a ports-and-adapters design; first-class Rails and RubyLLM integration. Your memories live in your own database — no external memory service.
pikuri-tasks gives a pikuri-core agent an in-memory task list it can use to plan and track multi-step work. A +Pikuri::Tasks::List+ holds the per-Agent state; four tools (+task_create+, +task_in_progress+, +task_completed+, +task_delete+) mutate it via content-as-identifier (no item IDs to hallucinate). +Pikuri::Tasks::Extension+ wires the list and tools onto an +Pikuri::Agent+ via +c.add_extension(...)+ inside the +Agent.new+ block. The list lives in process memory only — nothing is written to disk. Sub-agents do not inherit the parent's list (consistent with the "sub-agents do not inherit extensions" rule).
= dm-is-published This plugin makes it very easy to add different states to your models, like 'draft' vs 'live'. By default it also adds validations of the field value. Originally inspired by the Rails plugin +acts_as_publishable+ by <b>fr.ivolo.us</b>. == Installation # Add GitHub to your RubyGems sources $ gem sources -a http://gems.github.com $ (sudo)? gem install kematzy-dm-is-published <b>NB! Depends upon the whole DataMapper suite being installed, and has ONLY been tested with DM 0.10.0 (next branch).</b> == Getting Started First of all, for a better understanding of this gem, make sure you study the '<tt>dm-is-published/spec/integration/published_spec.rb</tt>' file. ---- Require +dm-is-published+ in your app. require 'dm-core' # must be required first require 'dm-is-published' Lets say we have an Article class, and each Article can have a current state, ie: whether it's Live, Draft or an Obituary awaiting the death of someone famous (real or rumored) class Article include DataMapper::Resource property :id, Serial property :title, String ...<snip> is :published end Once you have your Article model we can create our Articles just as normal Article.create(:title => 'Example 1') The instance of <tt>Article.get(1)</tt> now has the following things for free: * a <tt>:publish_status</tt> attribute with the value <tt>'live'</tt>. Default choices are <tt>[ :live, :draft, :hidden ]</tt>. * <tt>:is_live?, :is_draft? or :is_hidden?</tt> methods that returns true/false based upon the state. * <tt>:save_as_live</tt>, <tt>:save_as_draft</tt> or <tt>:save_as_hidden</tt> converts the instance to the state and saves it. * <tt>:publishable?</tt> method that returns true for models where <tt>is :published </tt> has been declared, but <b>false</b> for those where it has not been declared. The Article class also gets a bit of new functionality: Article.all(:draft) => finds all Articles with :publish_status = :draft Article.all(:draft, :author => @author_joe ) => finds all Articles with :publish_status = :draft and author == Joe Todo Need to write more documentation here.. == Usage Scenarios In a Blog/Publishing scenario you could use it like this: class Article ...<snip>... is :published :live, :draft, :hidden end Whereas in another scenario - like in a MenuItem model for a Restaurant - you could use it like this: class MenuItem ...<snip>... is :published :on, :off # the item is either on the menu or not end == RTFM As I said above, for a better understanding of this gem/plugin, make sure you study the '<tt>dm-is-published/spec/integration/published_spec.rb</tt>' file. == Errors / Bugs If something is not behaving intuitively, it is a bug, and should be reported. Report it here: http://github.com/kematzy/dm-is-published/issues == Credits Copyright (c) 2009-07-11 [kematzy gmail com] Loosely based on the ActsAsPublishable plugin by [http://fr.ivolo.us/posts/acts-as-publishable] == Licence Released under the MIT license.
pikuri-memory gives a pikuri-core agent durable, long-lived memory: facts about the user and their work that persist across conversations. It wires a +recall+ tool plus an automatic per-turn prefetch onto an agent via +c.add_extension Pikuri::Memory::Extension.new(...)+ inside the +Agent.new+ block — same opt-in shape as +pikuri-tasks+ / +pikuri-vectordb+. Recall is automatic and synchronous (embed + vector search, milliseconds); capture is automatic and asynchronous (an off-the-interaction-path extraction queue), so a turn never blocks on "what should I remember?". Storage is mem0 (https://github.com/mem0ai/mem0) reached over a thin Faraday HTTP client — the append-only +add+ / read-time +search+ model. Only the *user's own words* are fed to extraction (a write-side hygiene rule that structurally drops system/assistant/tool-sourced junk), and recalled context enters the chat as a +:system+ message so it is provenance-tagged and excluded from the next extraction pass. This release ships the Ruby client + extension + tool against a *bring-your-own* mem0 endpoint; a self-managed mem0 sidecar supervisor (the +ChromaServer+-style docker pattern) is a follow-on.
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.
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.