hi_score - npm Package Compare versions

Comparing version 1.7.8 to 1.7.9

js/app-ex01/ex01.08_app.js

@@ -17,3 +17,3 @@ /**
       'js/vendor/pcss.cfg-1.4.6.js',
-      'js/vendor/jquery-3.4.1.js',
+      'js/vendor/jquery-3.5.1.js',
       'js/plugin/jquery.deferred.whenAll-1.0.0.js',
@@ -20,0 +20,0 @@ 'js/vendor/jquery.event.dragscroll-1.0.0.js',

js/app-tb02/tb02.08_app.js

@@ -19,3 +19,3 @@ /*
       'js/vendor/pcss.cfg-1.4.6.js',
-      'js/vendor/jquery-3.4.1.js',
+      'js/vendor/jquery-3.5.1.js',
       'js/plugin/jquery.deferred.whenAll-1.0.0.js',
@@ -22,0 +22,0 @@ 'js/vendor/jquery.event.gevent-1.1.6.js',

package.json

@@ -13,9 +13,9 @@ {
     "apply-patch": "0.1.2",
-    "aws-sdk": "2.532.0",
+    "aws-sdk": "2.686.0",
     "azure-storage": "2.10.3",
-    "coveralls": "3.0.6",
-    "dotenv": "8.1.0",
-    "diff": "4.0.1",
-    "eslint": "6.4.0",
-    "eslint-plugin-json": "1.4.0",
+    "coveralls": "3.1.0",
+    "dotenv": "8.2.0",
+    "diff": "4.0.2",
+    "eslint": "7.1.0",
+    "eslint-plugin-json": "2.1.1",
     "express": "4.17.1",
@@ -26,3 +26,3 @@ "flow": "0.2.3",
     "istanbul": "0.4.5",
-    "jquery": "3.4.1",
+    "jquery": "3.5.1",
     "jquery.event.dragscroll": "1.0.0",
@@ -33,8 +33,8 @@ "jquery.event.gevent": "1.1.6",
     "jquery.urianchor": "1.3.5",
-    "jsdom": "15.1.1",
+    "jsdom": "16.2.2",
     "line-by-line": "0.1.6",
-    "mongodb": "3.3.2",
-    "mysql2": "1.7.0",
+    "mongodb": "3.5.8",
+    "mysql2": "2.1.0",
     "nodeunit": "0.11.3",
-    "npm": "6.13.4",
+    "npm": "6.14.5",
     "open-sans-fontface": "1.4.0",
@@ -45,7 +45,7 @@ "powercss": "1.4.6",
     "serve-index": "1.9.1",
-    "shelljs": "0.8.3",
+    "shelljs": "0.8.4",
     "taffydb": "2.7.3",
-    "uglify-js": "3.6.0",
+    "uglify-js": "3.9.4",
     "uglifycss": "0.0.29",
-    "websocket": "1.0.30"
+    "websocket": "1.0.31"
   },
@@ -130,3 +130,3 @@ "eslintConfig": {
   },
-  "version": "1.7.8",
+  "version": "1.7.9",
   "xhi_commandTable": [
@@ -651,5 +651,5 @@ [
           "check_filename": "node_modules/uglify-js/lib/scope.js",
-          "patch_filename": "uglify-js-3.5.11.patch",
+          "patch_filename": "uglify-js-3.9.4.patch",
           "pattern_str": "^\\s*// hi_score patch applied",
-          "relative_name": "patch/uglify-js-3.5.11.patch"
+          "relative_name": "patch/uglify-js-3.9.4.patch"
         },
@@ -661,8 +661,2 @@ {
           "relative_name": "patch/font-awesome-4.7.0.patch"
-        },
-        {
-          "check_filename": "node_modules/jquery/dist/jquery.js",
-          "patch_filename": "jquery-3.4.1.patch",
-          "pattern_str": "^\\s*window.jQuery = jQuery;$",
-          "relative_name": "patch/jquery-3.4.1.patch"
         }
@@ -669,0 +663,0 @@ ]

README.md

@@ -70,3 +70,3 @@ ![hi_score][_0A]
 
-We should now see the **Typebomb 2** web app in a browser and may use the
+You should now see the **Typebomb 2** web app in a browser and may use the
 developer tools to inspect the CSS, the DOM, and the JavaScript. Notice how
@@ -121,3 +121,3 @@ everything is production-ready including compressed CSS class names (yes, we
 ### Find help
-The lifecycle stages supported by `bin/xhi` are shown below. Those marked `placeholder` are those we plan to address in future releases. We use the command `bin/xhi help all` to see the entire list as shown below.
+The lifecycle stages supported by `bin/xhi` are shown below. Those marked `placeholder` are those we plan to address in future releases. Use the command `bin/xhi help all` to see the entire list as shown below.
 
@@ -151,3 +151,3 @@ ```
 
-We use `bin/xhi design` to see the Architecture Guide, Style Guide, or Visual Design Guide (VDG). Detailed help on a stage or range of stages is shown with the `-v` flag shown below.
+Use `bin/xhi design` to see the Architecture Guide, Style Guide, or Visual Design Guide (VDG). Detailed help on a stage or range of stages is shown with the `-v` flag shown below.
 
@@ -176,3 +176,3 @@ ```
 ### Run lifecycle stages
-We run a range of lifecycle steps as shown below.
+Run a range of lifecycle steps as shown below.
 
@@ -226,10 +226,10 @@ ```
 #### Goal dependencies
-Goal dependencies are stages that are *always* run before before a target stage. For example, if we run `bin/xhi dev_commit` the `dev_lint`, and `dev_test` stages will *always* be run first to ensure the code quality is acceptable.  If either requirement fails, `bin/xhi` exits immediately (with an exit code of 1) and the target stage is not attempted. Goal dependencies are defined in `package.json.xhi_commandTable`. We don't suggest changing them without careful consideration, but you can.
+Goal dependencies are stages that are *always* run before before a target stage. For example, if we run `bin/xhi dev_commit` the `dev_lint`, and `dev_test` stages will *always* be run first to ensure the code quality is acceptable.  If either requirement fails, `bin/xhi` exits immediately (with an exit code of 1) and the target stage is not attempted. Goal dependencies are defined in `package.json.xhi_commandTable`. Don't change these without careful consideration and testing.
 
 #### Environment dependencies
-Environment dependencies must be successfully completed in the development environment before the target stage. For example, if we run `bin/xhi dev_commit` but have not run `bin/xhi install`, the `install` stage will be run before the `dev_commit` stage. The success or failure of each stage is saved in the state file (`run/xhi_state.json`) and the next stage is run. If the `install` stage succeeds it will not be included in future steps for `dev_commit` as it will have been completed in the prior run. Environment dependencies are defined in `package.json.xhi_commandTable`. Again, we don't suggest changing them without careful consideration.
+Environment dependencies must be successfully completed in the development environment before the target stage. For example, if we run `bin/xhi dev_commit` but have not run `bin/xhi install`, the `install` stage will be run before the `dev_commit` stage. The success or failure of each stage is saved in the state file (`run/xhi_state.json`) and the next stage is run. If the `install` stage succeeds it will not be included in future steps for `dev_commit` as it will have been completed in the prior run. Environment dependencies are defined in `package.json.xhi_commandTable`. Don't change these without careful consideration and testing.
 
 Previously completed environment dependencies may be invalidated. For example, if `bin/xhi install` or `bin/xhi upgrade` fail, the tool will mark the `install` stage as failed and the stage will be attempted again in the next invocation that requires this stage as a dependencies.
 
-Explicitly requested stages will always run regardless of their last success status. For example, `bin/xhi dev_lint` may or may not run the `install` stage, but `bin/xhi install,dev_lint` will *always* run the `install` stage because it is explicitly listed. `bin/xhi help-dev_lint` will also run `install` since it is explicitly within the range provided (`help-dev_lint`). We reset the status by removing the `stage_status_map` from the `run/xhi_state.json` file.
+Explicitly requested stages will always run regardless of their last success status. For example, `bin/xhi dev_lint` may or may not run the `install` stage, but `bin/xhi install,dev_lint` will *always* run the `install` stage because it is explicitly listed. `bin/xhi help-dev_lint` will also run `install` since it is explicitly within the range provided (`help-dev_lint`). Reset the status by removing the `stage_status_map` from the `run/xhi_state.json` file.
 
@@ -342,4 +342,2 @@ ### Exit status
 
-Stay tuned for a more detailed example of this in mid-2019.
-
 ---
@@ -414,10 +412,10 @@ ## Vendor assets
 cd js/vendor
-cp jquery-3.4.1.js jquery-3.4.1.js.O
+cp jquery-3.5.1.js jquery-3.5.1.js.O
 
-# Now change jquery-3.4.1.js as required
+# Now change jquery-3.5.1.js as required
 
 # And create the diff
 cd ../..
-diff -u js/vendor/jquery-3.4.1.js.O js/vendor/jquery-3.4.1.js
-  > patch/jquery-3.4.1.patch
+diff -u js/vendor/jquery-3.5.1.js.O js/vendor/jquery-3.5.1.js
+  > patch/jquery-3.5.1.patch
 ```
@@ -532,3 +530,3 @@
 
-Sorry Gandalf but we don't mean *Magic* in a good way. Sure, we'll be able to create that sample-TODO-application-designed-to-impress-the-CTO in record time because of the built-in-demo-on-rails. But once one moves away from the demo even a little bit, things tend to go south fast. The build path from source code to the rendered HTML + CSS + JavaScript (**HCJ**) is so complex that it's impossible for a human to trace. When it breaks - and it will - all that *Magic* becomes *Evil Curses*. That's because these **Tower of Babel** solutions have traded HTML + CSS + Javascript for a Mötley Crüe of transpiled languages that are often larger, more numerous, harder to learn, poorly documented, poorly integrated, and much easier to break.  Problems that should be easy to solve - like adding an app to share an existing app's resources - can become impossible.
+Sorry Gandalf but we don't mean *Magic* in a good way. Sure, we'll be able to create that sample-TODO-application-designed-to-impress-the-CTO in record time because of the built-in-demo-on-rails. But once one moves away from the demo even a little bit, things tend to go south fast. The build path from source code to the rendered HTML + CSS + JavaScript (**HCJ**) is so complex that it's impossible for a human to trace. When it breaks - and it will - all that *Magic* becomes *Evil Curses*. That's because these **Tower of Babel** solutions have traded HTML + CSS + Javascript for a Mötley Crüe of transpiled languages that are often larger, more numerous, harder to learn, poorly documented, poorly integrated, and much easier to break.  Problems that should be easy to solve - like adding an app to share resources - can be effectively impossible.
 
@@ -540,3 +538,3 @@ `hi_score` is designed to avoid the [Tower of Babel](#towers-of-babel), automate processes **around** the **HCJ**, and help the developers continuously improve their skills and understanding on the **core technologies** of web apps. We hope you like it.
 ### Linux, Ubuntu or Debian Based
-When using Ubuntu Linux 16.04+ or a derivative -- such a Linux Mint, Kubuntu, Xubuntu, Lubuntu, or similar -- simply ensure the following libraries are installed. One can simply run the attached commands one at a time to ensure all prerequisites are met.
+When using Ubuntu Linux 16.04+ or a derivative -- such a Linux Mint, Kubuntu, Xubuntu, Lubuntu, or similar -- ensure the following libraries are installed. Run the attached commands one at a time to ensure all prerequisites are met.
 
@@ -547,5 +545,4 @@ ```
     libfile-slurp-perl liblist-moreutils-perl \
-    net-tools \
-    openssh-server pandoc pandoc-citeproc \
-    unzip zip
+    net-tools openssh-server pandoc pandoc-citeproc \
+    unzip zip;
 
@@ -578,3 +575,3 @@ # Install recommended libraries
 ### Macintosh Prerequisites
-We found Mac High Sierra worked after the following.
+Mac High Sierra worked with the following commands:
 
@@ -589,3 +586,3 @@ ```bash
 ### Windows 10 Prerequisites
-In theory, the Windows Subsystem for Linux running an Ubuntu distro should work as with the prerequisites [listed above](#linux-ubuntu-or-debian-based). However, we haven't tested it. On may also use the virutal appliance detailed above.
+In theory, the Windows Subsystem for Linux running an Ubuntu distro should work as with the prerequisites [listed above](#linux-ubuntu-or-debian-based). However, we haven't tested it. One may also use the virutal appliance detailed above.
 
@@ -625,3 +622,3 @@ Return to the [Quick Start](#quick-start)
 ### IDE Configuration
-We provide configs for JetBrain's IDE IntelliJ or Webstorm in the repository.  Other IDEs will work fine, but we will need to manually adjust them to support the code style. The good news is we should only need to do this once per IDE and then it can be added to the repository. Contributions for VSCode, VIM, and other environments are welcome.
+We provide configs for JetBrain's IDE IntelliJ or Webstorm in the repository.  Other IDEs will work fine, but you will need to manually adjust them to support the code style. One should only need to do this once per IDE and then it can be added to the repository. Contributions for VSCode, VIM, and other environments are welcome.
 
@@ -628,0 +625,0 @@

Fixed alerts

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

Found 1 instance in 1 package

Improved metrics

Number of low supply chain risk alerts

10

decreased by-9.09%

Worsened metrics

Total package byte prevSize

10628233

decreased by-2.2%

Number of package files

148

decreased by-10.3%

Lines of code

14993

decreased by-25.66%

Number of lines in readme file

866

decreased by-0.35%

No dependency changes