tree 11dc12a5a841c95bcc7176208262a740d7648093
parent ac2fc7d830460742b774a9a9ff1d5a9ee3626c2f
author Gunnar Mills <gmills@us.ibm.com> 1563921127 -0500
committer Gunnar Mills <gmills@us.ibm.com> 1564586711 +0000

Remove carets from package.json

caret (^)

    backwards compatible new functionality
    old functionality deprecated, but operational
    large internal refactor
    bug fix

Some of the packages were already missing carets.
This better reflects our package management, we have a npm 5
package-lock.json that is intended to lock the repo down to
a specific set of versions of packages to help our build
reliability, and insulate us a little from the NPM stability
issues.

When the Web UI was still in its infancy, OpenBMC got burned from
this. What NPM called "Compatible with version" introduced build
failures overnight without a code change.

Found in some package-lock.json documentation:
"A specific version in package.json guarantees the version only at
the top level."

npm update, npm audit fix, npm-check-updates will still
behave the same.

This is helps a future commit that moves to a
package-lock.json generated by npm 6.

npm 6 changes package-lock.json from exact versions to loosly
versions.
tilde and caret will be added to the package-log.json.
See:
https://github.com/npm/npm/issues/20434
https://github.com/npm/npm/issues/20891

Tested: Build and loaded on a Witherspoon
Change-Id: Ie28f5b903f71215285df07c650a58c11037efccd
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>