ng update does not really touch karma-jasmine and typescript packages

[BryanWilhite]

i notice that blindly updating karma-jasmine related packages can break things; what is the recommended guidance?

> npm outdated

Package                       Current    Wanted   Latest  Location
@types/jasmine                 2.8.16    2.8.16   3.5.10  songhay-ng-workspace
@types/node                  12.12.34  12.12.34  13.11.0  songhay-ng-workspace
@types/numeral                 0.0.25    0.0.25   0.0.26  songhay-ng-workspace
core-js                        2.6.11    2.6.11    3.6.4  songhay-ng-workspace
jasmine-core                   2.99.1    2.99.1    3.5.0  songhay-ng-workspace
jasmine-spec-reporter           4.2.1     4.2.1    5.0.1  songhay-ng-workspace
karma-chrome-launcher           2.2.0     2.2.0    3.1.0  songhay-ng-workspace
karma-jasmine                   1.1.2     1.1.2    3.1.1  songhay-ng-workspace
karma-jasmine-html-reporter     0.2.2     0.2.2    1.5.3  songhay-ng-workspace
ts-node                         7.0.1     7.0.1    8.8.2  songhay-ng-workspace
tslint                         5.11.0    5.11.0    6.1.1  songhay-ng-workspace

[BryanWilhite]

this is the guidance from Google:

If your project depends on other Angular libraries, we recommend that you consider updating to their latest version. In some cases this update might be required in order to resolve API incompatibilities. Consult ng update or npm outdated to learn about your outdated libraries.