Update package.json

[john-md86]

Suggestion of repair for problem found through npm audit. Updating this package will probably solve the problem. Procedure suggested by the npm website itself

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[john-md86]

I signed it!

[googlebot]

CLAs look good, thanks!

[johnjbarton]

Travis fails with

INVALID COMMIT MSG: does not match "<type>(<scope>): <subject>" !

[ffflabs]

@johnjbarton
@SantiagoCJ

Unfortunately, log4js has loggly as an optional dependency, which is installed by npm@6 even if you do it with --no-optional.

loggly hasn't been updated in 2 years and has 6 vulnerabilities due to the fact of using outdated version of request and a dependency on timespan that has no patch.

So, even if using the latest log4js version (2.7.0), karma will generate a warning for those 6 vulnerabilities.

I reported this in log4js repo: log4js-node/log4js-node#716