Bindings for Go ABI and tooling to integrate Go code.
Communicating sequential processes for node. Go style concurrency with channels.
KNX protocol implementation for Node.js, support KNX/IP Tunneling/Routing, KNX/IP Secure and Data Secure, FT1.2/KBerry TP plain KNXas well as full secure KNX stack. This is the ENGINE of Node-Red KNX-Ultimate node. Go check it!
Load Google GO files as any javascript modules under nodeJS runtime.
An IPC implementation between Node and its child process (Golang binary) using the stdin / stdout as the transport.
SockJS-node is a server counterpart of SockJS-client a JavaScript library that provides a WebSocket-like object in the browser. SockJS gives you a coherent, cross-browser, Javascript API which creates a low latency, full duplex, cross-domain communication
Port of Log4js to work with node.
Create and package prebuilds for native modules
Stripe API wrapper
General client library for the new dYdX system (v4 decentralized)
Native Abstractions for Node.js: C++ header for Node 0.8 -> 26 compatibility
A Promisified layer over rhea AMQP client
extended POSIX-style sprintf
Buffer-backed Streams for reading and writing.
Implementation of window.fetch which can use http2 seamlessly
Simple XML to JavaScript object converter.
n8n node for Kommo Api
The Adobe PDF Services Node.js SDK provides APIs for creating, combining, exporting and manipulating PDFs.
Official library for using the Slack Platform's Web API
This package is a web-compatible package manager built with tsserverlib compatibility in mind. It does not require a "real" filesystem or a "real" NPM installation, but instead uses [orogene](https://github.com/orogene/orogene) to perform package manageme
A debug logger package for other Google libraries
Traceloop Software Development Kit (SDK) for Node.js
Node.js Streams, a user-land copy of the stream library from Node.js
LZ-based compression algorithm
Idiomatic Ruby bindings for PDF Oxide. Process, analyze, and generate PDFs through the libpdf_oxide cdylib used by the Python, Java, Node, Go, and C# bindings.
Sibling gem to `blockchain0x`. Verify inbound x402 payments + issue x402-aware HTTP calls. Wire-format byte-equivalent with the Node, Python, and Go ports.
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.
FAP is a ruby gem build on top of the excellent Nokogiri, to turn boring XML, or HTML documents into yummy ruby objects. Right now, it only support using Nokogiri's XPath selectors, and simple "relations" between a document nodes, though this will hopefully get better. FAP's ideas are loosely connected to tools built by some adventurous fellas at AF83, who still do PHP things to their brains. Some credits should go to them, and to the horrid weather that kept me locked inside last week-end. And yes, I know it's a stupid name. But I'm sure you can come up with a decent acronym. :)
Zz structures are an interesting way of representing relations invented by Ted Nelson, whose domain model I provide in a gem Yzz. In this gem, YNelson, I combine Yzz with the universal Petri net provided by YPetri (another gem I wrote) to obtain a hybrid data structure that formalizes and generelizes a spreadsheet. Because let us note spreadsheets (as I have seen them) can be considered Petri nets of a kind, with cell functions acting as Petri net transitions. At the same time, spreadsheets are globally orthogonal structures with 3 typical dimensions (rows, columns and sheets). By using zz structures, the globally orthogonal spreadsheet is generalized as a locally orthogonal zz structure, with relations represented as zz dimensions, thus generalizing and formalizing a spreadsheet. The catch is that I have not yet finished the thinking process regarding what everything should be a zz object: Places (cells) and transitions definitely yes, but how about nets and dimensions? Should YNelson go as far as making namespaces into zz objects? The reason why these questions are hard to answer is because Ted Nelson himself, while providing interfaces guidelines (zz structure views, cursors...) did not comment on these questions. While being a (textual) DSL, YNelson aims to provide convenience on par with actual spreadsheet apps. Unlike YPetri, YNelson also aims to be able to specify more than one Petri net node per command, but this is still under development. See the user guide and the documentation for the details. YNelson documentation is available online, but due to formatting issues, you may prefer to generate the documentation on your own by running rdoc in the gem directory. For an example of how YPetri can be used to model complex dynamical systems, see the eukaryotic cell cycle model which I released as "cell_cycle" gem.
Diff and patch tables
Diff and patch tables
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.