A dead-simple, cli-based task journaler.
Monkey patches React to notify you about avoidable re-renders.
Temporary file and directory creator
A pure JS HTTP parser for node.
Library for Signing and Verifying JWTs that use DIDs as issuers and JWEs that use DIDs as recipients
Resolve DID documents
A list of CSS features and their positions in the process of becoming implemented web standards
An Argon2 library for Node
No description provided.
Resolve DID documents from an https domain
Infer the content-type of a request.
A "1:1 output" JavaScript port of Potrace JS for NodeJS.
Ceramic did:key method resolver
Lightweight buffer library for the browser (Now with Base64URL support!)
A WebCrypto Polyfill for NodeJS
syntax, type definitions and schemas for atproto handles, DIDs and DID documents
Types and related utilities for TypeScript
Create and verify W3C Verifiable Credentials and Presentations in JWT format
Resolve DID documents for Ethereum addresses and public keys
This package exports the number `214` and it's name is also two hundred and fourteen characters long which is the longest name currently allowed by the npm registry to see how a name that long would look if you did it.
Fuzzy match a command from a list (typo-safety)
No description provided.
A library for managing DIDs (Decentralized Identifiers) and associated data.
high-performance Node.js WebSocket engine for Socket.IO
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.
Contentful API wrapper library exposing an ActiveRecord-like interface