Set up a modern Node.js app by running one command
Determine an app's root path from anywhere inside the app
Make your own error types!
A small utility for packing files in a flatpak.
Port of Log4js to work with node.
Node.js Streams, a user-land copy of the stream library from Node.js
Node.js native addon build tool
Open stuff like URLs, files, executables. Cross-platform.
Better `os.arch()` for node and the browser -- detect OS architecture
larksuite open sdk for nodejs
Minimal web-style fetch TypeScript typings
Koa web app framework
A lightweight toolset for writing styles in Javascript.
Streaming http in the browser
Node-API implementation for Emscripten
Make a directory and its parents if needed - Think `mkdir -p`
Regular expression for matching a shebang line
process information for node.js and browsers
Lightweight Node.js version sniffing/comparison
Smaller distribution of node-pty.
PostgreSQL client - pure javascript & libpq with the same API
Create and package prebuilds for native modules
Fixes stack traces for files with source maps
Babel preset used by Create React App
The intention of this library is to make it easy to build up a structure of nodes which will then be output to a flat file. Imagine using this library as part of a web-app that makes it easy to manipulate images in a structured, visual way (without say, Photoshop).
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
No description provided.
No description provided.
No description provided.