Check whether a given string matches the `PotentialCustomElementName` production as defined in the HTML Standard.
HTTP server mocking and expectations library for Node.js
MCP server for interacting with Azure DevOps
ant design renderer set for the jsonforms declarative form framework
Type safe mocking library for TypeScript
Vue 3 compatibility build for Vue 2
Static analysis tool for JavaScript
A JavaScript library for internationalization and localization that leverages the official Unicode CLDR JSON data.
A Gemfile.lock parser for Node.js represented with JSON.
Tests whether one path is inside another path
Fluid container loader
rehype plugin to create alerts (admonitions/callouts)
Find and load configuration from a package.json property, rc file, TypeScript module, and more!
Polygon tesselation library, ported from SGI's GLU implementation.
ES Math-related intrinsics and helpers, robustly cached.
Analyzers for Dead Code/Types and termination
The MetaMask Node module template
API testing framework core
An eslint rule that searches for potential secrets/keys in code
Support GitHub-style alerts for markdown-it
TypeScript definitions for is-potential-custom-element-name
Detect potential issues with users system that could prevent Yeoman from working correctly
TypeScript definitions for valid-url
This package is part of Magic xpa Web Application Framework. It is used to easily create modern business apps powered by Angular to provide a rich user experience and meet the increasingly complex enterprise business expectations for digital transformati
Potential Expectations — a composable, graph-driven agent runtime for Rust
Agent registry and builder for Potential Expectations — manifest-driven agent construction and discovery
Agent bus for Potential Expectations — in-process transport, logged bus, and negotiate()
Core types for Potential Expectations — messages, channels, state, traits
Graph execution engine for Potential Expectations — state graphs, Pregel model, ReAct topology, and builder DSL
OpenAI-compatible LLM provider for Potential Expectations
Procedural macros for Potential Expectations — derive and attribute macros for agents, tools, and state
Matrix reasoning and empirical routing for Potential Expectations — tensor operations, convergence detection, and empirical logging
Memory and checkpointing for Potential Expectations — SurrealDB store, cache layer, and conversation checkpoints
Prebuilt agent topologies for Potential Expectations — ReAct agent, messages state, tool conditions, and middleware
Async runtime for Potential Expectations — execution lifecycle, event bus, streaming, and metrics
Task management for Potential Expectations — structured work items, dependency DAG, lifecycle hooks, and agent tools
Polidef is a convience API for managing complex and potentially stateful conditionals through policy objects. Complex conditionals are fragile and can require a lot of state to exist in order to execute as expected. Polidef seeks to simplify implementation and testing so you spend less time wrangling conditional state and more time doing other things.
The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `<` lower than - `>=` lower than or equal - `><` included in list, items should be separated by `|` - `!><` not included in list, items should be separated by `|` - `~` pattern matching, may include `%` (any characters) and `_` (one character) - `!~` pattern not matching, may include `%` (any characters) and `_` (one character)