Build is broken

[dokterbob]

When using Node LTS Gallium, as specified in .nvmrc, when doing a clean install (after rm -rf node_modules), we're getting the following error on npm install (see full debug log attached):

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @vue/cli-plugin-eslint@4.5.15
npm ERR! Found: eslint@7.32.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^7.6.0" from the root project
npm ERR!   peer eslint@"^7.5.0 || ^8.0.0" from @babel/eslint-parser@7.17.0
npm ERR!   node_modules/@babel/eslint-parser
npm ERR!     dev @babel/eslint-parser@"^7.16.5" from the root project
npm ERR!   4 more (@vue/eslint-config-airbnb, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@">= 1.6.0 < 7.0.0" from @vue/cli-plugin-eslint@4.5.15
npm ERR! node_modules/@vue/cli-plugin-eslint
npm ERR!   dev @vue/cli-plugin-eslint@"~4.5.15" from the root project
[2022-06-27T11_36_20_781Z-debug-0.log](https://github.com/ipfs-search/dweb-search-frontend/files/8991588/2022-06-27T11_36_20_781Z-debug-0.log)

npm ERR! 
npm ERR! Conflicting peer dependency: eslint@6.8.0
npm ERR! node_modules/eslint
npm ERR!   peer eslint@">= 1.6.0 < 7.0.0" from @vue/cli-plugin-eslint@4.5.15
npm ERR!   node_modules/@vue/cli-plugin-eslint
npm ERR!     dev @vue/cli-plugin-eslint@"~4.5.15" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /Users/drbob/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/drbob/.npm/_logs/2022-06-27T11_36_20_781Z-debug-0.log

This is currently blocking @Szeket as well as #210 and perhaps more. eresolve-report.txt 2022-06-27T11_36_20_781Z-debug-0.log

[dokterbob]

Initial research suggests it's a bug/incompatibility in later NPM versions as older versions aren't installing either.

[dokterbob]

The problem doesn't occur with npm@7.24.2.

[dokterbob]

It also doesn't occur with npm install --legacy-peer-deps