manyfest 1.0.0

package/.config/luxury-extras/MySQL/Dockerfile_LUXURYCODE_MySQL

@@ -0,0 +1,65 @@
+# Use the codercom/code-server image
+FROM codercom/code-server:latest
+MAINTAINER steven velozo
+
+VOLUME /home/coder/.config
+VOLUME /home/coder/.vscode
+
+RUN echo "...installing debian dependencies..."
+RUN sudo apt update
+RUN sudo apt install vim curl tmux -y
+RUN sudo apt install default-mysql-server default-mysql-client -y
+# RUN sudo apt install sysv-rc-conf -y
+
+RUN echo "Building RETOLD development image..."
+
+RUN echo "...configuring mariadb (mysql) server..."
+RUN sudo sed -i "s|bind-address|#bind-address|g" /etc/mysql/mariadb.conf.d/50-server.cnf
+ADD ./.config/luxury-extras/MySQL/MySQL-Security.sql /home/coder/MySQL-Configure-Security.sql
+ADD ./.config/luxury-extras/MySQL/MySQL-Laden-Entry.sh /usr/bin/MySQL-Laden-Entry.sh
+RUN sudo chmod +x /usr/bin/MySQL-Laden-Entry.sh
+RUN ( sudo mysqld_safe --skip-grant-tables --skip-networking & ) && sleep 5 &&  mysql -u root < /home/coder/MySQL-Configure-Security.sql
+
+# Enable MariaDB even without systemd
+# RUN sudo sysv-rc-conf --level 0123456S mariadb on
+
+# Import the initial database
+RUN sudo service mariadb restart && sleep 5 && mysql -u root -p"123456789" -e "CREATE DATABASE YOURDATABASENAMEHERE;"
+
+RUN echo "...installing vscode extensions..."
+RUN code-server --install-extension ritwickdey.LiveServer \
+    code-server --install-extension hbenl.vscode-mocha-test-adapter \
+    code-server --install-extension hbenl.vscode-test-explorer \
+    code-server --install-extension hbenl.test-adapter-converter \
+    code-server --install-extension daylerees.rainglow \
+    code-server --install-extension oderwat.indent-rainbow \
+    code-server --install-extension evan-buss.font-switcher \
+    code-server --install-extension vscode-icons-team.vscode-icons \
+    code-server --install-extension bengreenier.vscode-node-readme \
+    code-server --install-extension bierner.color-info \
+    code-server --install-extension dbaeumer.vscode-eslint \
+    code-server --install-extension PKief.material-icon-theme
+
+SHELL ["/bin/bash", "-c"]
+USER coder
+
+# Copy any default configs for the coding environment we want (e.g. dark theme)
+# COPY ./.config/.default_home/ /home/coder/
+
+RUN echo "...mapping library specific volumes..."
+# Volume mappings for code
+VOLUME /home/coder/YOURLIBRARYNAMEHERE
+# VOLUME /home/coder/YOURLIBRARYNAMEHERE/node_modules
+
+RUN echo "...installing node version manager..."
+# Because there is a .bashrc chicken/egg problem, we will create one here to simulate logging in.  This is not great.
+RUN touch ~/.bashrc && chmod +x ~/.bashrc
+RUN curl https://raw.githubusercontent.com/creationix/nvm/master/install.sh | bash
+
+RUN echo "...installing node version 14 as the default..."
+RUN . ~/.nvm/nvm.sh && source ~/.bashrc && nvm install 14
+RUN . ~/.nvm/nvm.sh && source ~/.bashrc && nvm alias default 14
+
+WORKDIR /home/coder/YOURLIBRARYNAMEHERE
+
+ENTRYPOINT ["/usr/bin/MySQL-Laden-Entry.sh"]

package/.config/luxury-extras/MySQL/MySQL-Laden-Entry.sh

@@ -0,0 +1,17 @@
+#!/bin/bash
+
+trap 'kill -TERM $PID' TERM INT
+
+/usr/bin/entrypoint.sh --bind-addr "0.0.0.0:8080" . &
+
+PID=$!
+
+sleep 2
+
+sudo service mariadb restart
+
+wait $PID
+trap - TERM INT
+wait $PID
+EXIT_STATUS=$?
+echo "Service exited with status ${EXIT_STATUS}"

package/.config/luxury-extras/MySQL/MySQL-Security.sql

@@ -0,0 +1,5 @@
+FLUSH PRIVILEGES;
+
+ALTER USER 'root'@'localhost' IDENTIFIED BY '123456789';
+
+GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' IDENTIFIED BY '123456789' WITH GRANT OPTION;

package/.vscode/launch.json

@@ -0,0 +1,46 @@
+{
+    // Use IntelliSense to learn about possible attributes.
+    // Hover to view descriptions of existing attributes.
+    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
+    "version": "0.2.0",
+    "configurations": [
+        {
+            "name": "Launch Debug Harness",
+            "type": "pwa-node",
+            "request": "launch",
+            "outputCapture": "std",
+            "skipFiles": [
+                "<node_internals>/**"
+            ],
+            "program": "${workspaceFolder}/debug/Harness.js",
+            "presentation": {
+                "hidden": false,
+                "group": "",
+                "order": 1
+            }
+        },
+        {
+            "name": "Mocha Tests",
+            "args": [
+                "-u",
+                "tdd",
+                "--timeout",
+                "999999",
+                "--colors",
+                "${workspaceFolder}/test"
+            ],
+            "internalConsoleOptions": "openOnSessionStart",
+            "program": "${workspaceFolder}/node_modules/mocha/bin/_mocha",
+            "request": "launch",
+            "skipFiles": [
+                "<node_internals>/**"
+            ],
+            "type": "pwa-node",
+            "presentation": {
+                "hidden": false,
+                "group": "",
+                "order": 2
+            }
+        }
+    ]
+}

package/Dockerfile_LUXURYCode

@@ -0,0 +1,39 @@
+# Use the codercom/code-server image
+FROM codercom/code-server:latest
+MAINTAINER steven velozo
+
+VOLUME /home/coder/.config
+VOLUME /home/coder/.vscode
+
+RUN echo "...installing debian dependencies..."
+RUN sudo apt update
+RUN sudo apt install vim curl tmux -y
+
+RUN echo "Building development image..."
+
+RUN echo "...installing vscode extensions..."
+RUN code-server --install-extension ritwickdey.LiveServer \
+    code-server --install-extension hbenl.vscode-mocha-test-adapter \
+    code-server --install-extension hbenl.vscode-test-explorer \
+    code-server --install-extension hbenl.test-adapter-converter \
+    code-server --install-extension daylerees.rainglow \
+    code-server --install-extension oderwat.indent-rainbow
+
+RUN echo "...mapping library specific volumes..."
+# Volume mappings for code
+VOLUME /home/coder/manyfest
+# VOLUME /home/coder/manyfest/node_modules
+
+SHELL ["/bin/bash", "-c"]
+USER coder
+
+RUN echo "...installing node version manager..."
+# Because there is a .bashrc chicken/egg problem, we will create one here to simulate logging in.  This is not great.
+RUN touch ~/.bashrc && chmod +x ~/.bashrc
+RUN curl https://raw.githubusercontent.com/creationix/nvm/master/install.sh | bash
+
+RUN echo "...installing node version 14 as the default..."
+RUN . ~/.nvm/nvm.sh && source ~/.bashrc && nvm install 14
+RUN . ~/.nvm/nvm.sh && source ~/.bashrc && nvm alias default 14
+
+WORKDIR /home/coder/manyfest

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2022 Steven Velozo
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,234 @@
+# Manyfest
+
+## JSON Object Manifest for Data Description and Parsing
+
+We focus so much on documentation and description for the mechanics of data at rest, in software development.  Schema for databases.  Well-named variables in code, with comments.  Expressive languages for writing software or querying graphs of information.
+
+As data crosses these boundaries, though, context is lost.  We reinvent the wheel at each layer!  The front-end code has its own mechanism for putting a label before a value to the user.  It is rare that there are less than three representations of an important piece of data across:
+
+* The Data Persistence Engine _(e.g. a SQL server table, or schemaless storage)_
+* Middle Tier Source Code _(e.g. an API service)_
+* Front End Source Code _(e.g. the code behind for a single page app)_
+* The User Interface _(e.g. a label on a web form)_
+
+Manyfest's purpose is to solve this problem by creating a simple pattern to describe, validate, manipulate and interpret data.
+
+![Official Mascot](https://github.com/stevenvelozo/manyfest/raw/main/diagrams/Mascot.jpg)
+
+_Man-E-Faces approves of Manyfest!_
+
+## Where Does this Run
+
+Either of a stand-alone library in node.js software, or, a dependency-free browser library.
+
+### Compatiblity
+
+This library is tested for node.js versions 8 through 16, and will likely work in future versions.  It is implemented as a simple set of es6 classes.
+
+The browser version has been packaged into a minified as well as an expanded debuggable library.  Sourcemaps are included.
+
+## Installation
+
+For use within node.js, run the following in the folder with your `package.json` file:
+
+```
+npm install --save Manyfest
+```
+
+Then, you can include it in your source code as follows:
+
+```
+const libManyfest = require('Manyfest');
+
+// Construct a Manyfest with a few defined columns
+let animalManyfest = new libManyfest(
+    {
+        "Scope": "Animal",
+        "Descriptors":
+            {
+                "IDAnimal": { "Name":"Database ID", "Description":"The unique integer-based database identifier for an Animal record.", "DataType":"Integer" },
+                "Name": { "Description":"The animal's colloquial species name (e.g. Rabbit, Dog, Bear, Mongoose)." },
+                "Type": { "Description":"Whether or not the animal is wild, domesticated, agricultural, in a research lab or a part of a zoo.." }
+            }
+    });
+
+// Make up a cute and furry test creature
+let testAnimal = {IDAnimal:8675309, Name:'BatBrains', Type:'Lab', Color:'Brown'};
+
+// Validate an Object Against the Manyfest
+let validateResults = animalManyfest.validate(testAnimal);
+
+console.log(JSON.stringify(validateResults,null,4));
+```
+
+The code above sets up a Manyfest, and runs a validation on the testAnimal.  The validation will come back all good telling us which properties aren't in the object but are described.  If the `strict` option has been set, missing described elements of an object without data are treated as errors.  If there are any `Required` columns, they are always errors if they are missing.
+
+Error does not mean the software throws an exception.  It comes back as well-formed JSON.
+
+## Lexicon
+
+Below is a lexicon of terms used throughout this documentation.  If you see anything missing, want more elaboration or just dislike a particular term, please file an issue in github!
+
+| Term | Description |
+| Scope | The scope of this representation; generally the clustered or parent record name (e.g. Animal, User, Transaction, etc.) -- does not have functional purpose; only for information and logging. |
+| Schema | The stateful representation of an object's structural definition. |
+| Element | A defined element of data in an object. |
+| Address | The address where that data lies in the object. |
+| Descriptor | A description of an element including data such as Name, NameShort, Hash, Description, and other important properties. |
+| Name | The name of the element.  Meant to be the most succinct human readable name possible. |
+| NameShort | A shorter name for the element.  Meant to be useful enough to identify the property in log lines, tabular views, graphs and anywhere where we don't always want to see the full name. |
+| Description | A description for the element.  Very useful when consuming other APIs with their own terse naming standards (or no naming standards)! |
+| Hash | A unique within this scope string-based key for this element.  Used for easy access of data. |
+| Constraint | A validation constraint for an element such as MaxLength, MinLength, Required, Default and such. |
+
+## A More Advanced Schema Example
+
+Addresses are meant to be kinda magic.  They describe locations in nested JSON just as well as simple objects.  Further, they can allow us to manipulate and read JSON values at specific addresses.
+
+
+Let's use our Animal schema and extend it a little bit.  In this case, a new JSON sub object needs to be included carrying important medical information about this animal.
+
+```
+let animalManyfest = new libManyfest(
+    {
+        "Scope": "Animal",
+        "Descriptors":
+            {
+                "IDAnimal": { "Name":"Database ID", "Description":"The unique integer-based database identifier for an Animal record.", "DataType":"Integer" },
+                "Name": { "Description":"The animal's colloquial species name (e.g. Rabbit, Dog, Bear, Mongoose)." },
+                "Type": { "Description":"Whether or not the animal is wild, domesticated, agricultural, in a research lab or a part of a zoo.." },
+                "MedicalStats": 
+                    {
+                        "Name":"Medical Statistics", "Description":"Basic medical statistics for this animal"
+                    },
+                "MedicalStats.Temps.MinET": { "Name":"Minimum Environmental Temperature", "NameShort":"MinET", "Description":"Safest minimum temperature for this animal to survive in."},
+                "MedicalStats.Temps.MaxET": { "Name":"Maximum Environmental Temperature", "NameShort":"MaxET", "Description":"Safest maximum temperature for this animal to survive in."},
+                "MedicalStats.Temps.CET":
+                    {
+                        "Name":"Comfortable Environmental Temperature",
+                        "NameShort":"Comf Env Temp",
+                        "Hash":"ComfET",
+                        "Description":"The most comfortable temperature for this animal to survive in."}
+            }
+    });
+```
+
+Notice in this example, the addresses are more complex.  They have a dot syntax.  This notifies Manyfest that they are nested values.  Further, there is both a Name and a NameShort descriptor setup.  This gives us a framework for consistently referring to the data element both internally and to the user.  It is no longer a mystery what someAnimal.MedicalStats.Temps.CET means.  Developers, user interface designers, database engineers, product managers and other folks who work on the software side don't have to maintain a third body of documentation about what the data means.
+
+To aid in this discovery, reference and such, we've given it a NameShort (for use in things like tabular views and graphs/charts), a longer Name and a Hash (to enable easy reading and writing using the object element read/write functions described later in this documentation).
+
+## Reading and Writing Element Properties
+
+Lastly, when working with objects, Manyfest provides a set of functions to read and write from/to these element addresses.  This can be useful for consistently accessing objects across boundaries as well as filling out element defaults without requiring a crazy amount of boilerplate code.
+
+### An Example and the Why of Reading and Writing Element Properties
+
+For instance, if you have an element with the address of "MedicalStats.HeartRate.RestingHeartRate.OverallAverage" (which is very verbose; most JSON object structures are not so descriptive) it would take a significant amount of code to write that to an empty object.
+
+#### The Typical Javascript Way of Reading
+
+In the example below, the read and write code throws an error.  You could work around it with:
+
+* a bunch of sequential guards
+* use fancy new es6 syntax with the `someObject.?SomeContainer.?OtherContainer.Property` _(although that isn't compatible with older services and browsers that run older versions of javascript)_
+* write some kind of complex handler for it
+* something else clever?
+
+```
+// Write Code
+let newAnimal = {};
+
+// This is going to make a terrible error happen
+newAnimal.MedicalStats.HeartReat.RestingHeartRate.OverallAverage = 61;
+```
+
+```
+// Read Code
+let newAnimal = {};
+
+// This is going to make a terrible error happen
+console.log(newAnimal.MedicalStats.HeartReat.RestingHeartRate.OverallAverage);
+
+// My javascript interpreter said this when I tried this code:
+// > Uncaught TypeError: Cannot read properties of undefined (reading 'HeartReat')
+```
+
+#### The Manyfest Way
+
+However with the Manyfest reading and writing methods you can do this (all in one example since it doesn't blow up):
+
+```
+let newAnimal = {};
+
+// You can now try to access the value on a "clean" object...
+console.log(animalManyfest.getValueAtAddress(newAnimal, "MedicalStats.HeartRate.RestingHeartRate.OverallAverage"));
+
+// The output prints out "undefined" ... because it is!
+
+// This will be helpful and create the necessary structure inbetween
+animalManyfest.setValueAtAddress(newAnimal, "MedicalStats.HeartRate.RestingHeartRate.OverallAverage", 61);
+
+// You can now access the value as well...
+console.log(animalManyfest.getValueAtAddress(newAnimal, "MedicalStats.HeartRate.RestingHeartRate.OverallAverage"));
+
+// The output prints out "61"
+```
+
+#### That's Not All!
+
+Because we have mappings to and from more human readable names to the addresses, we can happily use either the Name or Hash for these lookups.  For instance, from the example above, if we have our Comfortable Environmental Temperature for an animal which was in the address `someAnimal.MedicalStats.Temps.CET` and had a hash of `ComfET`, a developer could easily access it by hash (assuming the `favoriteAnimalAPI` function returns a JSON representation of my favorite animal):
+
+```
+let favAnimal = favoriteAnimalAPI();
+
+console.log(animalManyfest.getValueByHash(favAnimal,'ComfET'));
+```
+
+For any elements that haven't defined a Hash, the Address is used.  This allows code to gracefully fall back.
+
+## Programmatically Defining a Schema
+
+Sometimes we don't have schemas, and want to define object element structure on the fly.  This can be done programmatically.  As a refresher, here is how we loaded our simplest schema manifest above:
+
+```
+const libManyfest = require('Manyfest');
+
+// Construct a Manyfest with a few defined columns
+let animalManyfest = new libManyfest(
+    {
+        "Scope": "Animal",
+        "Descriptors":
+            {
+                "IDAnimal": { "Name":"Database ID", "Description":"The unique integer-based database identifier for an Animal record.", "DataType":"Integer" },
+                "Name": { "Description":"The animal's colloquial species name (e.g. Rabbit, Dog, Bear, Mongoose)." },
+                "Type": { "Description":"Whether or not the animal is wild, domesticated, agricultural, in a research lab or a part of a zoo.." }
+            }
+    });
+```
+
+The programmatic equivalent is the following code:
+
+```
+const libManyfest = require('Manyfest');
+
+// Construct a Manyfest with a few defined columns
+let animalManyfest = new libManyfest();
+
+// Set the Scope
+animalManyfest.Scope = "Animal";
+
+// Add descriptors
+animalManyfest.addDescriptor("IDAnimal", { "Name":"Database ID", "Description":"The unique integer-based database identifier for an Animal record.", "DataType":"Integer" });
+animalManyfest.addDescriptor("Name", { "Description":"The animal's colloquial species name (e.g. Rabbit, Dog, Bear, Mongoose)." });
+animalManyfest.addDescriptor("Type", { "Description":"Whether or not the animal is wild, domesticated, agricultural, in a research lab or a part of a zoo.." });
+
+// Now you can work with the animalManyfest just as we did in the other method.
+```
+
+Programmatic definition is interesting because you can start with a pre-defined manifest and add on elements later if you like.  This can be useful if you, say, have an endpoint which generally returns a record, but, sometimes decorates it with connected records for developer convenience.
+
+## Other Uses
+
+Have you ever tried to code against a weather API?  They use *so many* different structures of data.  And once you've used their structure, you are kindof stuck with it.
+
+With manyfest, you can easily create a description for each API and code against getting values by hash.  This abstracts the complexity of multiple API services without requiring you to marshal it into your own persistence format.

package/debug/Harness.js

@@ -0,0 +1,20 @@
+let libManyfest = require(`../source/Manyfest.js`);
+
+let animalManyfest = new libManyfest(
+    {
+        "Scope": "Animal",
+        "Descriptors":
+            {
+                "IDAnimal": { "Name":"Database ID", "Description":"The unique integer-based database identifier for an Animal record.", "DataType":"Integer" },
+                "Name": { "Description":"The animal's colloquial species name (e.g. Rabbit, Dog, Bear, Mongoose)." },
+                "Type": { "Description":"Whether or not the animal is wild, domesticated, agricultural, in a research lab or a part of a zoo.." }
+            }
+    });
+
+// Make up a cute and furry test creature
+let testAnimal = {IDAnimal:8675309, Name:'BatBrains', Type:'Lab', Color:'Brown'};
+
+// Check the Manyfest
+let checkResults = animalManyfest.validate(testAnimal);
+
+console.log(JSON.stringify(checkResults,null,4));

package/gulpfile.js

@@ -0,0 +1,62 @@
+'use strict';
+
+const libBrowserify = require('browserify');
+const libGulp = require('gulp');
+
+const libVinylSourceStream = require('vinyl-source-stream');
+const libVinylBuffer = require('vinyl-buffer');
+
+const libTerser = require('gulp-terser');
+const libBuble = require('gulp-buble');
+const libSourcemaps = require('gulp-sourcemaps');
+const libGulpUtil = require('gulp-util');
+
+// Build the module for the browser
+//   This gulp task is taken from the gulp recipe repository:
+//   https://github.com/gulpjs/gulp/blob/master/docs/recipes/browserify-uglify-sourcemap.md
+libGulp.task('minified',
+() => {
+	// set up the custom browserify instance for this task
+	var tmpBrowserify = libBrowserify(
+	{
+		entries: './source/Manyfest-Browser-Shim.js',
+		standalone: 'Fable',
+		debug: true
+	});
+
+	return tmpBrowserify.bundle()
+		.pipe(libVinylSourceStream('manyfest.min.js'))
+		.pipe(libVinylBuffer())
+		.pipe(libSourcemaps.init({loadMaps: true}))
+				// Add transformation tasks to the pipeline here.
+				.pipe(libTerser())
+				.on('error', libGulpUtil.log)
+		.pipe(libSourcemaps.write('./'))
+		.pipe(libGulp.dest('./dist/'));
+});
+
+// Build the module for the browser
+//   This gulp task is taken from the gulp recipe repository:
+//   https://github.com/gulpjs/gulp/blob/master/docs/recipes/browserify-uglify-sourcemap.md
+libGulp.task('debug',
+	() => {
+		// set up the custom browserify instance for this task
+		var tmpBrowserify = libBrowserify(
+		{
+			entries: './source/Manyfest-Browser-Shim.js',
+			standalone: 'Manyfest',
+			debug: true
+		});
+
+		return tmpBrowserify.bundle()
+			.pipe(libVinylSourceStream('manyfest.js'))
+			.pipe(libVinylBuffer())
+					.on('error', libGulpUtil.log)
+			.pipe(libGulp.dest('./dist/'));
+	});
+
+libGulp.task
+(
+	'build',
+	libGulp.series('debug', 'minified')
+);

package/package.json

@@ -0,0 +1,67 @@
+{
+  "name": "manyfest",
+  "version": "1.0.0",
+  "description": "JSON Object Manifest for Data Description and Parsing",
+  "main": "index.js",
+  "scripts": {
+    "docker-dev-build-image": "docker build ./ -f Dockerfile_LUXURYCode -t retold/manyfest:local",
+    "docker-dev-run": "docker run -it -d --name manyfest -p 12340:8080 -v \"$PWD/.config:/home/coder/.config\"  -v \"$PWD:/home/coder/manyfest\" -u \"$(id -u):$(id -g)\" -e \"DOCKER_USER=$USER\" retold/manyfest:local",
+    "test": "./node_modules/mocha/bin/_mocha -u tdd -R spec",
+    "tests": "./node_modules/mocha/bin/_mocha -u tdd -R spec --grep"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/stevenvelozo/manyfest.git"
+  },
+  "keywords": [
+    "manifest",
+    "data",
+    "description",
+    "json"
+  ],
+  "mocha": {
+    "diff": true,
+    "extension": [
+      "js"
+    ],
+    "package": "./package.json",
+    "reporter": "spec",
+    "slow": "75",
+    "timeout": "5000",
+    "ui": "tdd",
+    "watch-files": [
+      "source/**/*.js",
+      "test/**/*.js"
+    ],
+    "watch-ignore": [
+      "lib/vendor"
+    ]
+  },
+  "devDependencies": {
+    "@babel/core": "^7.17.9",
+    "@babel/preset-env": "^7.16.11",
+    "@testing-library/dom": "^8.13.0",
+    "async": "^3.2.3",
+    "browserify": "^17.0.0",
+    "chai": "4.3.6",
+    "gulp": "^4.0.2",
+    "gulp-babel": "^8.0.0",
+    "gulp-buble": "^0.9.0",
+    "gulp-sourcemaps": "^3.0.0",
+    "gulp-terser": "^2.1.0",
+    "gulp-util": "^3.0.8",
+    "jsdom": "^19.0.0",
+    "mocha": "9.2.2",
+    "npm-check-updates": "^12.5.9",
+    "nyc": "^15.1.0",
+    "vinyl-buffer": "^1.0.1",
+    "vinyl-source-stream": "^2.0.0"
+  },
+  "dependencies": {},
+  "author": "steven velozo <steven@velozo.com>",
+  "license": "MIT",
+  "bugs": {
+    "url": "https://github.com/stevenvelozo/manyfest/issues"
+  },
+  "homepage": "https://github.com/stevenvelozo/manyfest#readme"
+}

package/source/Manyfest-Browser-Shim.js

@@ -0,0 +1,15 @@
+/**
+* @license MIT
+* @author <steven@velozo.com>
+*/
+
+/**
+* Manyfest browser shim loader
+*/
+
+// Load the manyfest module into the browser global automatically.
+var libManyfest = require('./Manyfest.js');
+
+if (typeof(window) === 'object') window.Manyfest = libManyfest;
+
+module.exports = libManyfest;

package/source/Manyfest-LogToConsole.js

@@ -0,0 +1,19 @@
+/**
+* @license MIT
+* @author <steven@velozo.com>
+*/
+
+/**
+* Manyfest simple logging shim (for browser and dependency-free running)
+*/
+
+const logToConsole = (pLogLine, pLogObject) =>
+{
+    let tmpLogLine = (typeof(pLogLine) === 'string') ? pLogLine : '';
+
+    console.log(`[Manyfest] ${tmpLogLine}`);
+
+    if (pLogObject) console.log(JSON.stringify(tmpLogObject,null,4)+"\n");
+};
+
+module.exports = logToConsole;