This is a collection of modules usable in Node.js v10+ environments, with a selected subset of these packages usable in most browsers via a transformer (e.g. Babel) and package bundlers.
I recommend adding any package from this repo to your dependencies field in your package.json for most cases, but if you plan to develop a package for the browser and your using a package bundler, add them to your devDependencies field instead.
Your going to need Git, Yarn and Node.js v10+
git clone https://github.com/futagoza/cm.git
cd cm
yarn install| package | release | dependency status | weight |
|---|---|---|---|
| @futagoza/child-process |  |
 |
|
| @futagoza/cli-utils |  |
 |
|
| @futagoza/core-js |  |
 |
|
| @futagoza/create-stream |  |
 |
|
| @futagoza/node-run |  |
 |
|
| @futagoza/publish-package |  |
 |
|
| @futagoza/pump |  |
 |
|
| @futagoza/sync-yarn-workspaces |  |
 |
|
| cm |  |
 |
|
| runasync |  |
 |
You'll find the documentation (if any) for each package in their respective directories and/or README.md file.
It is recommended to use a package (or if you prefer, web application) bundler in your projects build setup, so that you can cherry pick the modules you want to use from these packages via imports (that's what I made them for 😄). I recommend using one of these three:
The package's in this repository simply started as single file utility modules that I copy-pasted into other projects whenever I needed them. In 2012 I decided to make a dedicated package on NPM (first common, later cm) that I would just include via the dependencies field in my package.json files, but in less then a year it became a hassle to maintain as I wasn't the type to manage multiple projects. That has changed since late 2017 when I was able to give more time to some of my local projects; not to mention I'm really starting to need a set of central utility packages, so here's for attempt 5 🍺
Copyright © 2019 Futago-za Ryuu, https://github.com/futagoza
Released under the MIT License, http://opensource.org/licenses/MIT.