A simple tool to show and run code snippets in the node REPL
This package provides support for the [RedisBloom](https://redis.io/docs/data-types/probabilistic/) module, which adds additional probabilistic data structures to Redis.
Easy error subclassing and stack customization
demo on node examples
transform humanize time to ms
Library for interacting with OAuth 1.0, 1.0A, 2 and Echo. Provides simplified client access and allows for construction of more complex apis and OAuth providers.
Simple dependency graph.
Native Abstractions for Node.js: C++ header for Node 0.8 -> 26 compatibility
Generates and consumes source maps
A simple JavaScript implementation of Dijkstra's single-source shortest-paths algorithm.
pgvector support for Node.js, Deno, and Bun (and TypeScript)
A library for finding and using SSH public keys
Generates and consumes source maps
High performance Node.js image processing, the fastest module to resize JPEG, PNG, WebP, GIF, AVIF and TIFF images
this is basic node examples
This package provides support for the [RediSearch](https://redis.io/docs/interact/search-and-query/) module, which adds indexing and querying support for data stored in Redis Hashes or as JSON documents with the [RedisJSON](https://redis.io/docs/data-type
Google Sheets API -- simple interface to read/write data and manage sheets
An AMQP 0-9-1 (e.g., RabbitMQ) library and client.
zlib port to javascript - fast, modularized, with browser support
Check installed versions of node and npm
Actions Http Client
exiting a node.js process *and flushing stdout and stderr*
unist utility to check if a node passes a test
Implementation of the SPDY protocol on node.js.
(This gem was named as treevisitor) tree.rb is a 'clone' of tree unix command. The gem implements a library to mange tree structures. The gem contains also a library to build tree with a dsl (domain specific language), and an implementation of visitor design pattern. An example of DSL to build tree: <pre> tree = TreeNode.create do node "root" do leaf "l1" node "sub" do leaf "l3" end node "wo leaves" end </pre>
Detect USB devices when being connected and update a GOM sensor node accordingly. This allows to automagically avtivate the device mirror overlay on the horizon in home for example.
tulipmania - tulips on the blockchain; learn by example from the real world (anno 1637) - buy! sell! hodl! enjoy the beauty of admiral of admirals, semper augustus, and more; run your own hyper ledger tulip exchange nodes on the blockchain peer-to-peer over HTTP; revolutionize the world one block at a time
Safely evaluates code (Ruby and others) by sending it through https://eval.in == Languages and Versions Ruby | MRI 1.0, MRI 1.8.7, MRI 1.9.3, MRI 2.0.0, MRI 2.1 C | GCC 4.4.3, GCC 4.9.1 C++ | C++11 (GCC 4.9.1), GCC 4.4.3, GCC 4.9.1 CoffeeScript | CoffeeScript 1.7.1 (Node 0.10.29) Fortran | F95 (GCC 4.4.3) Haskell | Hugs98 September 2006 Io | Io 20131204 JavaScript | Node 0.10.29 Lua | Lua 5.1.5, Lua 5.2.3 OCaml | OCaml 4.01.0 PHP | PHP 5.5.14 Pascal | Free Pascal 2.6.4 Perl | Perl 5.20.0 Python | CPython 2.7.8, CPython 3.4.1 Slash | Slash HEAD x86 Assembly | NASM 2.07 == Example: It's this simple: result = EvalIn.call 'puts "example"', language: "ruby/mri-2.1" result.output # returns "example\n"
You can communicate with Dkron using a RESTful JSON API over HTTP. Dkron nodes usually listen on port `8080` for API requests. All examples in this section assume that you've found a running leader at `localhost:8080`. Dkron implements a RESTful JSON API over HTTP to communicate with software clients. Dkron listens in port `8080` by default. All examples in this section assume that you're using the default port. Default API responses are unformatted JSON add the `pretty=true` param to format the response.
`fingerpuppet` is a simple library and commandline tool to interact with Puppet's REST API without needing to have Puppet itself installed. This may be integrated, for example, into a provisioning tool to allow your provisioning process to remotely sign certificates of newly built systems. Alternatively, you could use it to request known facts about a node from your Puppet Master, or even to request a catalog for a node to, for example, perform acceptance testing against a new version of Puppet before upgrading your production master. Install the binford2k/fingerpuppet puppet module to get a class that can automatically configure your `auth.conf` file under Puppet Enterprise, where that file is managed.
LayeredYAMLConfig provides a simple config file that supports multiple layers. Values in the right or uppermost layers override values in lower layers. This makes it easy to share configuration without duplication while still allowing what needs to be different to vary. For example: program.default.conf program.server_foo.conf program.site_bar.conf program.conf Optionally, leaf nodes can be evaluated using as ERB templates, feeding the configuration into itself.
You can communicate with Dkron using a RESTful JSON API over HTTP. Dkron nodes usually listen on port `8080` for API requests. All examples in this section assume that you've found a running leader at `localhost:8080`. Dkron implements a RESTful JSON API over HTTP to communicate with software clients. Dkron listens in port `8080` by default. All examples in this section assume that you're using the default port. Default API responses are unformatted JSON add the `pretty=true` param to format the response.
Implement orderable trees in ActiveRecord using the nested set model, with multiple roots and scoping, and most importantly user-defined ordering of subtrees. Fetches preordered trees in one go, updates are write-heavy. This is a substantially butchered-up version/offspring of acts_as_threaded. The main additional perk is the ability to reorder nodes, which are always fetched ordered. Example: root = Folder.create! :name => "Main folder" subfolder_1 = Folder.create! :name => "Subfolder", :parent_id => root.id subfolder_2 = Folder.create! :name => "Another subfolder", :parent_id => root.id subfolder_2.move_to_top # just like acts_as_list but nestedly awesome root.all_children # => [subfolder_2, subfolder_1] See the rdocs for examples the method names. It also inherits the awesome properties of acts_as_threaded, namely materialized depth, root_id and parent_id values on each object which are updated when nodes get moved. Thanks to the authors of acts_as_threaded, awesome_nested_set, better_nested_set and all the others for inspiration.
Implement orderable trees in ActiveRecord using the nested set model, with multiple roots and scoping, and most importantly user-defined ordering of subtrees. Fetches preordered trees in one go, updates are write-heavy. This is a substantially butchered-up version/offspring of acts_as_threaded. The main additional perk is the ability to reorder nodes, which are always fetched ordered. Example: root = Folder.create! :name => "Main folder" subfolder_1 = Folder.create! :name => "Subfolder", :parent_id => root.id subfolder_2 = Folder.create! :name => "Another subfolder", :parent_id => root.id subfolder_2.move_to_top # just like acts_as_list but nestedly awesome root.all_children # => [subfolder_2, subfolder_1] See the rdocs for examples the method names. It also inherits the awesome properties of acts_as_threaded, namely materialized depth, root_id and parent_id values on each object which are updated when nodes get moved. Thanks to the authors of acts_as_threaded, awesome_nested_set, better_nested_set and all the others for inspiration.
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.