Feature/package install warnings

[andrewstec]

Warnings would be produced during yarn install command when no lockfile was used during the installation:

info No lockfile found.
[1/5] Validating package.json...
[2/5] Resolving packages...
warning workspace-aggregator-f34e4066-738c-4aea-a55c-2d330f1bb603 > autotest > xunit-viewer@5.2.0: xunit viewer has been upgraded to v6
warning workspace-aggregator-f34e4066-738c-4aea-a55c-2d330f1bb603 > portal-backend > xunit-viewer@5.2.0: xunit viewer has been upgraded to v6
warning workspace-aggregator-f34e4066-738c-4aea-a55c-2d330f1bb603 > portal-backend > supertest > superagent@3.8.3: Please note that v5.0.1+ of superagent removes User-Agent header by default, therefore you may need to add it yourself (e.g. GitHub blocks requests without a User-Agent header).  This notice will go away with v5.0.2+ once it is released.
warning workspace-aggregator-f34e4066-738c-4aea-a55c-2d330f1bb603 > autotest > xunit-viewer > babel-core > babel-register > core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning workspace-aggregator-f34e4066-738c-4aea-a55c-2d330f1bb603 > autotest > xunit-viewer > babel-core > babel-runtime > core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
[3/5] Fetching packages...
info fsevents@1.2.11: The platform "linux" is incompatible with this module.
info "fsevents@1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning Ignored scripts due to flag.
[5/5] Building fresh packages...

• Updating XUnit to version 6 eliminated "xunit-viewer@5.2.0: xunit viewer has been upgraded to v6" warning.
• Updating SuperTest to version 5 eliminated "Please note that v5.0.1+ of superagent removes User-Agent header by default" warning.
• Did NOT eliminate "core-js@<3 is no longer maintained and not recommended for usage due to the number of issues" warning because it is a clear dependency in the latest version of Onsen UI:
  
  From: https://github.com/OnsenUI/OnsenUI/blob/master/package.json
• Did NOT eliminate Linux environment-specific "warning sha.js@2.4.11: Invalid bin entry for "sha.js" (in "sha.js")", as Yarn is introducing a fix in a later release. See Allow dots in bin names yarnpkg/yarn#7811 and fix: yarn warning for invalid bin entry browserify/sha.js#65 for more details.

Sha.js issue will be resolved here: ubccpsctech#99

[andrewstec]

Here is the Yarn installation from the current Docker container build:

[rtholmes]

@andrewstec will CircleCI run on this PR automatically?

[winstan]

Fine...
But some of these changes don't do anything.... ^2.0.5 should be the same as ^2.0.8 and also ^4 the same as ^4.41.5... (caret meaning update to the latest minor version)

[andrewstec]

@andrewstec will CircleCI run on this PR automatically?

Hi Reid. It did: https://circleci.com/gh/ubccpsctech/classy/1217.

It looks like CircleCI did not send back the information to Github. If I re-run it, it will likely fix this PR pre-req.

[andrewstec]

Fine...
But some of these changes don't do anything.... ^2.0.5 should be the same as ^2.0.8 and also ^4 the same as ^4.41.5... (caret meaning update to the latest minor version)

In the case of "@types/supertest": "^2.0.8",, we could revert that line for the reason you said above.

In the other case, the more verbose convention is more widely used in the package.json file. Those were exceptions to the rule. They do not have to change though.

[andrewstec]

CircleCI is currently re-running to fix the pre-req status on this PR.

[winstan]

Fine...
But some of these changes don't do anything.... ^2.0.5 should be the same as ^2.0.8 and also ^4 the same as ^4.41.5... (caret meaning update to the latest minor version)

In the case of "@types/supertest": "^2.0.8",, we could revert that line for the reason you said above.

In the other case, the more verbose convention is more widely used in the package.json file. Those were exceptions to the rule. They do not have to change though.

I'm happy without any changes. :)