Results for node-gadgets

Real-time extraction from web pages of HTML gadgets and associated properties using node-dom based on given criterias

Tools for making a Nostr client.

CLI for llmist - run LLM agents from the command line

Testing utilities for llmist - mock LLM responses and test agents

An angular 2+ library for common gadgets.

Storage, management, compilation, and automatic deployment of MediaWiki gadgets.

Node.js Streams, a user-land copy of the stream library from Node.js

Determine if the current node version supports the `--preserve-symlinks` flag.

A light-weight module that brings Fetch API to node.js

Node.js API (Node-API)

Reusable React UI widgets - This is my widget library. There are many like it, but this one is mine...

AiPM Chat - an open-source, high-performance chatbot framework that supports speech synthesis, multimodal, and extensible Function Call plugin system. Supports one-click free deployment of your private ChatGPT/LLM web application.

Ignore is a manager and filter for .gitignore rules, the one used by eslint, gitbook and many others.

Load node modules according to tsconfig paths, in run-time or via API.

Browser PKI key material tools and reusable Private Key Gadgets API.

Browser-capability gadget hooks for ggui — declared via DataContract.clientCapabilities.gadgets, mounted by the UI generator's component code.

better fetch for Node.js. Works on any JavaScript runtime!

Cross platform child_process#spawn and child_process#spawnSync

A Babel preset that enables parsing of proposals supported by the current Node.js version.

Like which(1) unix command. Find the first instance of an executable in the PATH.

Determines if an object can be used as an array

Browser certificate investigation tools and reusable Certificate Gadgets API.

Provides a way to make requests

Vite as Node.js runtime

# Chef Data Region ## Description Chef Data Region extends the `Chef::DSL::DataQuery` module's `data_bag_item` method with the ability to dynamically expand the data bag name in a configurable, environment-specific manner. ## Motivation This gem exists to address the following scenario: An organization maintains data in Chef data bag items. The data is deployed to several data center environments and is stored in data bags whose names reference the environments. The organization wants to write environment-agnostic recipes that access the data bags without explicitly referencing the data bags by their environment names. As a concrete example, imagine the organization maintains encrypted data for three deployment environments: development, staging, and production. It maintains this data in three data bags, one for each environment, with data for services named `gadget` and `widget` in items: | Environment | Bag | Item | |-------------+----------------+--------| | Development | secure-dev | gadget | | Development | secure-dev | widget | | Production | secure-prod | gadget | | Production | secure-prod | widget | | Staging | secure-staging | gadget | | Staging | secure-staging | widget | The items are encrypted with a key unique to that environment to maximize security. Now consider how a recipe would access these bags. When then recipe is running, it needs to know the data center environment in order to construct the bag name. The organization would most likely assign the enviroment name to a node attribute. In a naive implementation, each recipe would include logic that examined the attribute's value to determine which bag to load. This would obviously duplicate code. Imagine instead that the organization wants to reference the bag by the name `secure` and rely on an _abstraction_ to translate `secure` into the environment-specific bag name. This gem provides that abstraction. ## Features This gem overrides the `data_bag_item` method with configurable logic that dynamically decides which bag to load. It retains API compatibility with `Chef::DSL::DataQuery#data_bag_item`, so existing recipes that call `data_bag_item` work without modification. The gem imposes no constraints on data bag item structure. ## Configuration Assign the region name to a node attribute that varies by environment: node.default['local'][region'] = 'staging' Add the following configuration to Chef Client's `client.rb` file. * Require the gem: require 'chef/data_region' * Configure the gem with a hash that maps a bag name to an expansion pattern: Chef::DataRegion.add( 'secure', { attribute: %w(local region), pattern: 'secure-%<attribute>s' } ) ## Bag name expansion The gem expands bag names using Ruby's `format` method. _More pending..._