when running npm install giving eslint depency issue

[furqanwasi]

node -v v20.5.0
MacOS

after running the command below
$ TIMETRACKER_URL=http://localhost:443/ npm run dev
get following logs and asks me Do you want to install 'webpack-cli' (yes/no): yes on yes it give below error

> [email protected] dev
> webpack-dev-server --inline --progress --config build/webpack.dev.conf.js

CLI for webpack must be installed.
  webpack-cli (https://github.com/webpack/webpack-cli)

We will use "npm" to install the CLI via "npm install -D webpack-cli".
Do you want to install 'webpack-cli' (yes/no): yes
Installing 'webpack-cli' (running 'npm install -D webpack-cli')...

when running npm install giving eslint dependency issue,

npm install

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^8.45.0" from the root project
npm ERR!   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/[email protected]
npm ERR!   node_modules/@eslint-community/eslint-utils
npm ERR!     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm ERR!     @eslint-community/eslint-utils@"^4.4.0" from [email protected]
npm ERR!     node_modules/eslint-plugin-vue
npm ERR!       dev eslint-plugin-vue@"^9.15.1" from the root project
npm ERR!     1 more (eslint-plugin-n)
npm ERR!   10 more (babel-eslint, eslint-config-standard, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^6.0.0 || ^7.0.0" from [email protected]
npm ERR! node_modules/eslint-loader
npm ERR!   dev eslint-loader@"^4.0.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^6.0.0 || ^7.0.0" from [email protected]
npm ERR!   node_modules/eslint-loader
npm ERR!     dev eslint-loader@"^4.0.2" 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! 
npm ERR! For a full report see:

Please advice thanks