Describe the bug
make all → npm install prints several upstream-deprecation warnings during a completely fresh install:
npm warn deprecated @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
npm warn deprecated eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
None of these are current CVEs (npm audit is clean, 0 vulnerabilities as of the last dependency pass), just stale/EOL'd upstream packages, mainly pulled in via eslint@8.x and its transitive deps. Still worth cleaning up since it's the first thing anyone sees on a brand new clone.
Expected behavior
A fresh make all install has no deprecation noise. Likely fix: bump eslint to 9.x + eslint-config-next to a matching version, which should cascade-fix the @humanwhocodes/* and rimraf warnings pulled in transitively.
Additional context
Good first issue: contained to frontend/package.json devDependencies + verifying npm run lint and next build still pass after the bump.
Describe the bug
make all→npm installprints several upstream-deprecation warnings during a completely fresh install:None of these are current CVEs (
npm auditis clean, 0 vulnerabilities as of the last dependency pass), just stale/EOL'd upstream packages, mainly pulled in viaeslint@8.xand its transitive deps. Still worth cleaning up since it's the first thing anyone sees on a brand new clone.Expected behavior
A fresh
make allinstall has no deprecation noise. Likely fix: bumpeslintto 9.x +eslint-config-nextto a matching version, which should cascade-fix the@humanwhocodes/*andrimrafwarnings pulled in transitively.Additional context
Good first issue: contained to
frontend/package.jsondevDependencies + verifyingnpm run lintandnext buildstill pass after the bump.