Get Clean Reading Content from every web page
Shared Zod 4 schemas for the velocity-node read API. Consumed by velocity-bridge-ui and velocity-explorer (and any future velocity-node consumer).
Read and parse a YAML file. A wrapper of js-yaml read file directly.
co wrapper for node-read
Blob & File implementation in Node.js, originally from node-fetch.
Wrapper for node read and write files API,
A lightweight Node.js module to recursively read files in a directory using ES6 Promises
The Node.js bindings of the humanfs library.
Contains parsers and serializers for ASN.1 (currently BER only)
SWC node register
smart-buffer is a Buffer wrapper that adds automatic read & write offset tracking, string operations, data insertions, and more.
Module for reading .pgpass
Load node modules according to tsconfig paths, in run-time or via API.
A node.js module for parsing form data, especially file uploads.
read and write binary structures and data types
Add support for more integer widths to Buffer
AWS credential provider that sources credentials from a Node.JS environment.
Reads a binary file to determine its CPU architecture.
fs read and write streams based on minipass
Get stdin as a string or Uint8Array
Easily read/write JSON files.
<!-- EDIT /Users/z/iuser/node/read/readme.md -->
utils for @node-minify
fs read and write streams based on minipass
redis client to write to master node and read from slave node
This gem can make Nodes and Edges data that are in txt transforming ruby objects.
This provides a read-only interace over the data provided by the date-holidays Node module available at https://github.com/commenthol/date-holidays .'
RubyNode is a library that allows read only access to Ruby's internal NODE structure.
acts_as_better_tree is great for anyone who needs a fast tree capable of handling millions of nodes without slowing down on writes like nestedset or on reads like a standard tree.
The initial focus is to read EAC-CPF files that represent an individual person, which will have a 'cpfDescription' node. The 'cpfDescription' (Corporate body, person or family description) contains information on the name structures, descriptive elements, and relationships.
rrg will read the source code of a Ruby project and generate a graph based on the require statements in the code; nodes represent the source files and an arrow from A to B means that A contains a `require 'B'` statement.
bocuse teaches chef-solo a few tricks. A strict front-end to chef-solo, it reads a configuration syntax that is under source control and generates JSON for chef-solo. This library puts the full power of Ruby at your fingertips when composing configuration for your nodes using templates and helpers. It is the missing link between puppet and chef.
This is the start of a Puppet provisioning system. It provides a graphical web service, a JSON rest API and command line interface that will manage Hiera YAML files and a few functions to read them and apply classes and parameters to a node. It works like a lightweight External Node Classifier. It also provides provisioning functionality to spin up new instances after classifying them. It currently has a backend for Cloud Provisioner and will shortly have a VMWare plugin to spin up new instances for Razor to provision. New backend plugins are quite easy to create. Documentation forthcoming.
Diggr is a ruby wrapper for the Digg API. Diggr strives to remain consistent with the Digg API endpoints listed here: http://apidoc.digg.com/CompleteList. Endpoints are created in Diggr with method calls. Each node in an endpoint becomes a method call and each node which is an argument becomes an argument to the previous method. As an example, the following endpoint /user/{user name} in which the user name is "johndoe" would be created with this Diggr call: diggr.user("johndoe") To send the request to the Digg API and retrieve the results of the call, Diggr requests are terminated in one of two ways. 1. Using the fetch method. By ending your request with the fetch method, your result will be returned to you. If the request is singular, you will receive a single object as a response. If the request is plural, you will receive a collection of objects stored in an array. 2. Using any Enumerable method. In this case, it is unnecessary to use the fetch method. See the synopsis for examples of each of these types of calls. Options such as count or offset can be set using the options method and providing a hash of arguments. See synopsis for more information. Note: In an effort to remain consistent with the Digg API, some method names do not follow the ruby idiom of underscores. Although somewhat ugly, this allows a user to read the Digg API and understand the exact methods to call in Diggr to achieve their desired results.
Diggr is a ruby wrapper for the Digg API. Diggr strives to remain consistent with the Digg API endpoints listed here: http://apidoc.digg.com/CompleteList. Endpoints are created in Diggr with method calls. Each node in an endpoint becomes a method call and each node which is an argument becomes an argument to the previous method. As an example, the following endpoint /user/{user name} in which the user name is "johndoe" would be created with this Diggr call: diggr.user("johndoe") To send the request to the Digg API and retrieve the results of the call, Diggr requests are terminated in one of two ways. 1. Using the fetch method. By ending your request with the fetch method, your result will be returned to you. If the request is singular, you will receive a single object as a response. If the request is plural, you will receive a collection of objects stored in an array. 2. Using any Enumerable method. This works only on plural requests. In this case, it is unnecessary to use the fetch method. See the synopsis for examples of each of these types of calls. Options such as count or offset can be set using the options method and providing a hash of arguments. See synopsis for more information. Note: In an effort to remain consistent with the Digg API, some method names do not follow the ruby idiom of underscores. Although somewhat ugly, this allows a user to read the Digg API and understand the exact methods to call in Diggr to achieve their desired results.
Diggr is a ruby wrapper for the Digg API. Diggr strives to remain consistent with the Digg API endpoints listed here: http://apidoc.digg.com/CompleteList. Endpoints are created in Diggr with method calls. Each node in an endpoint becomes a method call and each node which is an argument becomes an argument to the previous method. As an example, the following endpoint /user/{user name} in which the user name is "johndoe" would be created with this Diggr call: diggr.user("johndoe") To send the request to the Digg API and retrieve the results of the call, Diggr requests are terminated in one of two ways. 1. Using the fetch method. By ending your request with the fetch method, your result will be returned to you. If the request is singular, you will receive a single object as a response. If the request is plural, you will receive a collection of objects stored in an array. 2. Using any Enumerable method. In this case, it is unnecessary to use the fetch method. See the synopsis for examples of each of these types of calls. Options such as count or offset can be set using the options method and providing a hash of arguments. See synopsis for more information. Note: In an effort to remain consistent with the Digg API, some method names do not follow the ruby idiom of underscores. Although somewhat ugly, this allows a user to read the Digg API and understand the exact methods to call in Diggr to achieve their desired results.
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.