chore: Fix react linting error resulting in local make build failure

[alexweav]

Currently, running make build from the tip of main fails on my environment.

Unclear if this something specific to my environment or not.
Node version: v16.20.0
NPM version: 8.19.4

The error seems to stem from a lint failure in the react frontend:

ERROR in ./src/views/ViewStatus.tsx:76:40
TS7006: Parameter 'peer' implicitly has an 'any' type.
    74 |           <TableCell>
    75 |             <List>
  > 76 |               {data.cluster.peers.map((peer, i) => {
       |                                        ^^^^
    77 |                 return (
    78 |                   <ListItem disablePadding sx={{ display: 'list-item' }} key={i}>
    79 |                     <p>

ERROR in ./src/views/ViewStatus.tsx:76:46
TS7006: Parameter 'i' implicitly has an 'any' type.
    74 |           <TableCell>
    75 |             <List>
  > 76 |               {data.cluster.peers.map((peer, i) => {
       |                                              ^
    77 |                 return (
    78 |                   <ListItem disablePadding sx={{ display: 'list-item' }} key={i}>
    79 |                     <p>

webpack 5.75.0 compiled with 2 errors in 5263 ms
make: *** [Makefile:37: build-react-app] Error 1

This PR fixes the lint failure. Now, make build succeeds locally for me.

[alexweav]

I am not a react/JS expert by any means, so please let me know if there's a different preferred direction! I could not find any documented minimum version for tooling in CONTRIBUTING.md.

[gotjosh]

@Nexucis any thoughts?

[Nexucis]

that's odd you need to do this. This syntax shouldn't trigger the linter. I will take a look tomorrow (I'm off today).

As a side note, the PR looks totally ok.

[Nexucis]

Alright I tried on my side and look back at the CI/CD and in both context it doesn't trigger this issue. So it is certainly related to your environment.

Your npm and nodeJS version looks fine. Did you try with a fresher clone ? Perhaps there is something weird going on with the node_modules

[alexweav]

I did try cleaning/clearning node_modules to no avail... but you're right, this seems specific to my environment. I'll close this.