Fix: js dependency bump

[lsh-0]

No description provided.

[lsh-0]

I did a npm install and then an npm update then went through all of the security alerts and matched them to changes in the lock file. About half were satisfied and two were not present at all. The other half I added to the devDependencies section and ran npm install again.

Two dependencies are not present at all and I'm not sure what to do about them:

"dependencies": {
  "nwmatcher": ">=1.4.4"
}

"dependencies": {
  "macaddress": ">=0.2.9"
}

but I figure we'll get this very large change through and then figure those ones out.

[de-code]

Thank you for looking into this.

I upgraded webpack-cli. It is getting further but still failing.

[de-code]

it should pass ci now but at least locally isn't actually working yet.

[de-code]

It breaks with: zilverline/react-tap-event-plugin#121

[lsh-0]

nice catch

[de-code]

There are currently no end-to-end tests for the client. Therefore I would always sanity check any client library upgrades.

(There are end-to-end tests for the ETL though and smoke test for the Python server)

[de-code]

The client seems to be superficially working now. I somehow wiped my local data volume. I am running the ETL again to check it with actual data. This might take a while though.

[de-code]

Actually the ETL fails due to: https://github.com/elifesciences/issues/issues/5079 (which also failed in ci)

[de-code]

No update yet, I think I will focus on it after next Wed when I may do some other work on PeerScout. (https://github.com/elifesciences/issues/issues/5079 should be fixed first)

[lsh-0]

Thank you for the update, @de-code , we get bugged daily about it from github

[de-code]

Almost surprisingly this actually still worked.