Create a single object containing all data required to render a view/page that provides an event stream for syncing with server and data-binding. Browserify compatible.
Parses JSON-LD contexts
A TypeScript package with latest Schema.org Schema Typings
A tool for processing JSON-RPC messages
json parameterization module inspired from json-parameterization
JSON.parse with context information on error
JSON.parse with context information on error
This is an internal utility, not intended for public usage.
MCP plugin that saves 98% of your context window. Works with Claude Code, Gemini CLI, VS Code Copilot, OpenCode, and Codex CLI. Sandboxed code execution, FTS5 knowledge base, and intent-driven search.
View docs [here](https://radix-ui.com/primitives/docs/components/context-menu).
An output formatter for markdownlint-cli2 that produces the same output as markdownlint-cli
Base reporting library for istanbul
Model Context Protocol implementation for TypeScript
OpenTelemetry AsyncLocalStorage-based Context Manager
A flexible way to handle safe area, also works on Android and web.
unist utility to check if a node passes a test
micromark utility to resolve subtokens
Provide context info for eslint-plugin-import-x, so no extra arguments need to be added.
JSON.parse and stringify with better errors that respects formatting
A utility that converts rules made for checking the AST of `jsonc-eslint-parser` into rules compatible with `@eslint/json`.
Cloud executable protocol
Tiny helpers for processing regex syntax
Use json-context with leveldb. Contexts are automatically generated from matchers, and provides ability to watch matchers for realtime notifications.
TypeScript definitions for co-body
A meta-release of the json-ld gem including preloaded vocabularies for the Ruby RDF.rb library suite.
A zero-dependency Ruby gem for structured JSON logging with context merging, child loggers, level filtering, and pluggable outputs.
Context enriched logging with plain and json format.
A map impelementation with context, access goodies and representation format enhancements (json, yaml, xml,...)
Compact serialization format optimized for LLM contexts with 30-60% token reduction compared to JSON
`nvim-context` extracts live context from running Neovim instances via Unix socket connections, providing AI coding tools with cursor position, current file, visual selections, and diagnostics as JSON. It enables context-aware assistance by giving agents awareness of your current Neovim editor state, supporting questions like "What does this line do?" or analysis of selected code.
Implements the canonical log lines / wide events pattern. Accumulates context throughout a request lifecycle and emits a single structured JSON log line containing everything interesting.
{<img src="https://secure.travis-ci.org/socialcast/socialcast-shoulda-ext.png?branch=master" alt="Build Status" />}[http://travis-ci.org/socialcast/socialcast-shoulda-ext] = Socialcast Shoulda Extensions Adds new matchers and functionality to the shoulda test library = Installation In your Gemfile: group :test do gem 'socialcast_shoulda_ext', :git => 'git@github.com:socialcast/socialcast-shoulda-ext.git', :require => 'shoulda_ext' end If you want to include the trigger_callbacks matcher, also add the following to your test helper: ShouldaExt::Matchers::TriggerCallbackMatcher.attach_active_record_callback_hooks! = Matchers == RecordCountChangeMatcher Test if the count for a model has changed, and by how much. Requires the context_with_matcher_before_hooks patch, which is included by default. Provides the following matcher methods: - create_record(klass_or_symbol) Alias for change_record_count.for(klass_or_symbol).by(1) - create_records(klass_or_symbol, amount) Alias for change_record_count.for(klass_or_symbol).by(amount) - destroy_record(klass_or_symbol) Alias for change_record_count.for(klass_or_symbol).by(-1) - destroy_records(klass_or_symbol, amount) Alias for change_record_count.for(klass_or_symbol).by(-amount) - change_record_count Tests the difference in record count before and after the current setup/subject block Can be used with the follow methods: - for(klass_or_symbol) Provides the class which the test is being performed on. Can be a constant or a symbol - by(amount) Provides an expected difference for the number of records for the specified class. Excluding this number will allow the matcher to check for any difference Examples: context "creating a blog article" do context "with good parameters" do setup do post :create, :blog => {:title => 'my blog post', :body => 'Ipsum lorem...'} end should create_record :blog end context "without a body" do setup do post :create, :blog => {:title => 'my blog post' } end should_not create_record Blog end end == RespondWithJson Check if the controller's response is json Examples: context ":index.json" do setup do get :index, :format => 'json' end # Just check to see that the response was json should respond_with_json # Evaluate the hash produced by the json yourself should respond_with_json { |json| json.first['blog']['title'] == 'blog post 1'} # Provide an exact match should respond_with_json.exactly(['blog' => {'id' => 1, 'title' => 'blog post 1'}]) # Provide an exact match with a block should response_with_json.exactly{ |json| JSON.parse(Blog.all.to_json)} end context ":index.html" do setup do get :index end # or the negation should_not respond_with_json end == TriggerCallbackMatcher Test if create, update, destroy, or save callbacks were triggered. Requires running ShouldaExt::Matchers::TriggerCallbackMatcher.attach_active_record_callback_hooks! in your test suite in order to work properly. Examples: context "doing nothing to a record" do subject { Blog.new :title => 'blog title' } should_not trigger_callbacks end context "creating a record" do subject { Blog.create! :title => 'blog title' } should trigger_callbacks.for :create should_not trigger_callbacks.for :update, :destroy end = Integrations Currently only integrates with test/unit. RSpec support to come. = Shoulda Extensions == ContextWithMatcherBeforeHooks Adds the ability to define a 'before' method on any method which will be run before each context's setup/subject block. Used by RecordCountChangeMatcher to record the number of records before the tested operation takes place.
Captures unhandled exceptions from web requests and background jobs, enriches them with request/user/server context, and delivers structured JSON payloads to configurable webhook endpoints. Works with any Rack-based framework; optional Rails integration included.
Rails engine that tracks ActiveRecord create, update, and destroy events as structured JSON records. Ships a mountable web dashboard, whodunnit actor context, batch inserts via insert_all!, async writes via ActiveJob, time-travel reconstruction, RSpec matchers, Minitest assertions, and a migration path from PaperTrail.
Beautiful JSON Schema validation with Rails-native syntax, context-aware rules, and production-ready monitoring. Features include ActiveRecord-like schema definitions, multiple error message types, performance optimization with caching, internationalization support, and extensive Rails integration for APIs and web applications.
Logsy gives Rails apps one wide JSON event per request plus correlated breadcrumb logs, all tagged with whatever per-request context you set via Logsy[:key] = value. Tags propagate across background jobs. Generic JSON output to stdout — bring your own log shipper.
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.