No description provided.
OpenTelemetry instrumentation for `node:net` network API module
Web3 module to interact with the Ethereum nodes networking properties.
Form validation tool for @rescript/react
.Net dictionary for cspell.
The `@minecraft/server-net` module contains types for executing HTTP-based requests. This module can only be used on Bedrock Dedicated Server.
A Pulumi package for interacting with Docker in Pulumi programs
React Native TCP socket API for Android & iOS with SSL/TLS support
Observe when something in your node app starts listening on a TCP port
The Swagger API toolchain for .NET, Web API and TypeScript.
The Vercel Resource Provider lets you manage [Vercel](https://vercel.com) resources.
A Pulumi package to create TLS resources in Pulumi programs.
A Pulumi package for creating and managing Cloudflare cloud resources.
A Pulumi package for creating and managing Datadog resources.
Turn a function into an `http.Agent` instance
Use the Node `net` API in Chrome Apps
A tiny Node.js module to make any server force-closeable
TCP and IPC servers and clients for JavaScript
An Error subclass that will chain nested Errors and dump nested stacktraces
Cross-platform support for running Windows executables
Node-API bindings for .Net
A Pulumi package for creating and managing pagerduty cloud resources.
Generate a dep tree given a collection of manifests
TypeScript definitions for netease-captcha
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.
A comprehensive gem for Petri net modeling, colored Petri nets, matrix analysis, visualization, and formal verification for event sourcing and CRUD-to-Event mapping analysis. Part of the ORFEAS (Object-Relational to Event-Sourcing Architecture) framework.