In T200628#4470102, @MarcoAurelio wrote:

Those happen after running npm test as far as I can see on the zuul console. Where are the npm packages specified?

In package.json. These problematic packages are probably dependencies of dependencies of dependencies of dependencies of dependencies of packages we actually use.

So some cannot be fixed without upstream intervention I guess?

Current output as of January 2019:

npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info.
npm WARN deprecated circular-json@0.5.9: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated boom@4.3.1: This version is no longer maintained. Please upgrade to the latest version.

With the partial trees to trace the cause:

└─┬ eslint-config-wikimedia@0.10.0 
  └─┬ eslint@5.12.1 
    └─┬ file-entry-cache@2.0.0 
      └─┬ flat-cache@1.3.4 
        ├── circular-json@0.3.3

└─┬ grunt-jsonlint@1.1.0 
  └─┬ jsonlint@1.6.2 
    └─┬ nomnom@1.8.1

└─┬ webdriverio@4.12.0 
  └─┬ request@2.83.0 
    └─┬ hawk@6.0.2 
      └── boom@4.3.1

There are existing upstream tasks:

• for eslint, there's https://github.com/eslint/eslint/issues/11052 – looks like there'll be a release soon
• for jsonlint, there's https://github.com/zaach/jsonlint/issues/103, but the package is effectively abandonware, maybe we should switch to using eslint's JSON validating?
• for webdriverio, request stopped using hawk in https://github.com/request/request/commit/a6741d415aba31cd01e9c4544c96f84ea6ed11e3#diff-b9cfc7f2cdf78a7f4b91a753d10865a2 which landed in v2.87.0, but webdriverio is now on v5.x which seems to be a from-scratch re-write. Can we just bump to version 5?

The eslint issue was fixed in 0.11.0, which is now released and widely used.

For jsonlint, I've filed T220036 and https://github.com/wikimedia/eslint-config-wikimedia/issues/166.

Upgrading webdriverio to v.5 is T213268.

In T197901#5082949, @Jdforrester-WMF wrote:

Upgrading webdriverio to v.5 is T213268.

A quicker fix would be updating to the latest webdriverio v4 (4.12.0 > 4.14.4). I'll see if that fixes the problem.