Extending the array object for Node.js
TypeScript definitions for node-array-ext
Populate an observable array from node descriptors.
Simple dependency graph.
Type definitions for node-array-ext v1.0.00 from https://www.github.com/DefinitelyTyped/DefinitelyTyped
An ES7/ES2016 spec-compliant `Array.prototype.includes` shim/polyfill/replacement that works as far down as ES3.
Get the ArrayBuffer out of a TypedArray, robustly.
Fast JavaScript array sorting by implementing Python's Timsort algorithm
render domhandler DOM nodes to a string
Parse and stringify JSON with comments. It will retain comments even after saved!
ECMAScript (ESTree) AST walker
Determines if an object can be used as an array
Node default behavior import resolution plugin for eslint-plugin-import.
Returns an array of all tabbable DOM nodes within a containing node.
Walk any kind of tree structure depth- or breadth-first. Supports promises and advanced map-reduce operations with a very small API.
## Nodes List of nodes: - Foreach node (foreach-start, foreach-end, foreach-break) - Array map node (array-map-end, array-map-end-sync, array-map-break, array-map-start, array-map-start-sync) - Deep merge node (deep-merge) - Elastic logger node (elastic-l
Convert a typed array to a Buffer without a copy
Info about node `exports` field support: version ranges, categories, etc.
Like which(1) unix command. Find the first instance of an executable in the PATH.
Standalone CSS Selector Finder and Parser.
D3 sankey with circular links
Array manipulation, ordering, searching, summarizing, etc.
Constants and utilities about visitor keys to traverse AST.
Get an array of recursive directory contents
Allows shortcut APIs for LibXML Node to add arrays and hashes
Use with Chef-Solo. Grabs node info as array of Hashes or String ips.
Allows parsing nodenames or Nodesets in the way that Slurm generally handles, you can either fold an array of names into a nodeset, or you can expand a nodeset into an array of separate node names.
Deeply access nested Hash/Array data structures without checking for the existence of every node along the way.
Interface for very simple trees. You only have to implement parent (returns the single parent of the current node) and children (returns an Array of all the children of this node) and initialize. Drop this class in via include and presto!
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.