Core diff engine and affected package resolver
GraphQL IDE for better development workflows (GraphQL Subscriptions, interactive docs & collaboration).
Transform static class fields assignments that are affected by https://crbug.com/v8/12421
Wraps classes defined in computed keys of other classes affected by https://bugzilla.mozilla.org/show_bug.cgi?id=1887677
Node.js runfiles helpers for Bazel
Core components for creating a txwrapper lib.
Intuitive magical memoization library with Proxy and WeakMap
A professional solution for consolidating all your JavaScript projects in one Git repo
TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Supports MongoDB, MySQL, PostgreSQL and SQLite databases as well as usage with vanilla JavaScript.
Compare two objects using accessed properties with Proxy
True Affected - Semantic change detection for monorepos
No description provided.
A Cypress plugin for configurable accessibility analysis supporting WCAG 2.2 (A-AAA). It provides a detailed list of violations in the Cypress log, visual feedback directly in the Cypress runner as well as voice feedback, and generates a comprehensive, se
Ensures all `@dynamic-labs/*` packages in your project are running on the same version.
Extends Chai with lint-friendly terminating assertions.
Is this specifier a node.js core module?
Babel compiler core.
Fix the React 2 Shell vulnerability (CVE-2025-66478) in Next.js apps with one command
tldts core primitives (internal module)
Standard library
The `util.is*` functions introduced in Node v0.12.
Currents MCP server
Ruler — apply the same rules to all coding agents
The common dxp library for cli commands
DDDr stands for Domain Driven Design Repository. It's a Ruby gem that simplifies the implementation of data repositories in a Domain-Driven Design (DDD) architecture. It offers a clean interface for abstracting data access, allowing you to focus on your domain logic rather than database operations. With DDDr, you can easily swap out data sources without affecting your core business logic.
A "Productized Rails Application" is a single generic application having a hierarchical structure wherein add-ons and tweaks for concurrent versions of the application are possible without affecting the core "generic" code base. You might use this, for example, if you want to maintain a common shopping cart code base that all of your clients use, while still providing flexibility for paid add-ons or site-specific needs.
== Ruby Data Objects If you're building something in Ruby that needs access to a database, you may opt to use an ORM like ActiveRecord, DataMapper or Sequel. But if your needs don't fit well with an ORM—maybe you're even writing an ORM—then you'll need some other way of talking to your database. RDO provides a common interface to a number of RDBMS backends, using a clean Ruby syntax, while supporting all the functionality you'd expect from a robust database connection library: * Consistent API to connect to various DBMS's * Type casting to Ruby types * Time zone handling (via the DBMS, not via some crazy time logic in Ruby) * Native bind values parameterization of queries, where supported by the DBMS * Retrieve query info from executed commands (e.g. affected rows) * Access RETURNING values just like any read query * Native prepared statements where supported, emulated where not * Results given using simple core Ruby data types == RDBMS Support Support for each RDBMS is provided in separate gems, so as to minimize the installation requirements and to facilitate the maintenace of each driver. Many gems are maintained by separate users who work more closely with those RDBMS's. Due to the nature of this gem, most of the nitty-gritty code is actually written in C. See the official README for full details.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.