Command line todo application similar to Ruby on Rails 'rake notes', build for a .Net magazine tutorial.
OpenTelemetry instrumentation for `node:net` network API module
Web3 module to interact with the Ethereum nodes networking properties.
Text recoding in JavaScript for fun and profit!
The goal of this module is to find the best schematic layout for a set of `SchematicChip`s and `SchematicGroups` containing `SchematicPins` connected to each other with `SchematicTraces`
The `@minecraft/server-net` module contains types for executing HTTP-based requests. This module can only be used on Bedrock Dedicated Server.
.Net dictionary for cspell.
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
JSON Web Token implementation (symmetric and asymmetric)
The Swagger API toolchain for .NET, Web API and TypeScript.
The Vercel Resource Provider lets you manage [Vercel](https://vercel.com) resources.
semantic-release plugin to generate changelog content with conventional-changelog
A Pulumi package to create TLS resources in Pulumi programs.
A Pulumi package for creating and managing Cloudflare cloud resources.
<!--BEGIN STABILITY BANNER-->
A Pulumi package for creating and managing Datadog resources.
realistic password strength estimation
Use the Node `net` API in Chrome Apps
Turn a function into an `http.Agent` instance
TCP and IPC servers and clients for JavaScript
A tiny Node.js module to make any server force-closeable
Merges XLIFF files
Mail safe provides a safety net while you're developing an application that uses ActionMailer. It keeps emails from escaping into the wild. Once you've installed and configured this gem, you can rest assure that your app won't send emails to external email addresses. Instead, emails that would normally be delivered to external addresses will be sent to an address of your choosing, and the body of the email will be appended with a note stating where the email was originally intended to go.
Net::LDAP for Ruby (also called net-ldap) implements client access for the Lightweight Directory Access Protocol (LDAP), an IETF standard protocol for accessing distributed directory services. Net::LDAP is written completely in Ruby with no external dependencies. It supports most LDAP client features and a subset of server features as well. Net::LDAP has been tested against modern popular LDAP servers including OpenLDAP and Active Directory. The current release is mostly compliant with earlier versions of the IETF LDAP RFCs (2251-2256, 2829-2830, 3377, and 3771). Our roadmap for Net::LDAP 1.0 is to gain full <em>client</em> compliance with the most recent LDAP RFCs (4510-4519, plutions of 4520-4532). NOTE: This is a fork of https://github.com/ruby-ldap/ruby-net-ldap to support Ruby 1.8.7.
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.
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.