Find out exactly why Node is still running.
Node is running but you don't know why? why-is-node-running is here to help you.
Reliably determines if the code is running in Node.js
Cross Platform Smart Fetch Ponyfill
Cross platform child_process#spawn and child_process#spawnSync
The fastest and smallest JavaScript polygon triangulation library for your WebGL apps
Generates and consumes source maps
Run commands concurrently
An implementation of window.fetch in Node.js using Minipass streams
Low-level HTTP/HTTPS/XHR request interception library for NodeJS
Universal filesystem path utils
fast mysql driver. Implements core protocol, prepared statements, ssl and compression in native JS
A stand-alone types package for Undici
exiting a node.js process *and flushing stdout and stderr*
fs-extra contains methods that aren't included in the vanilla Node.js fs package. Such as recursive mkdir, copy, and remove.
Traverse an ESTree-compliant AST
General Language Independent Driver for the Enterprise (GLIDE) for Valkey
Native bindings for valkey-glide on linux-x64-gnu
Parse and stringify JSON with comments. It will retain comments even after saved!
Scanner and parser for JSON with comments.
Check if a file or directory exists in a given path.
Lint files staged by git
Check if stdout or stderr is interactive
A Test-Anything-Protocol library for JavaScript
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