Unable to build - "peer @vue/cli-service@"^4.3.1" from [email protected]"

[shoffmeister]

While trying to follow the build instructions (https://github.com/phil294/git-log--graph/blob/master/CONTRIBUTING.md), I get

git-log--graph on  master [!?] is 📦 v0.1.12 via  v18.18.0 
❯ cd web

git-log--graph/web on  master [!?] is 📦 v0.0.0-see-extension via  v18.18.0 
❯ npm i
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @vue/[email protected]
npm ERR! node_modules/@vue/cli-service
npm ERR!   dev @vue/cli-service@"~5.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @vue/cli-service@"^4.3.1" from [email protected]
npm ERR! node_modules/vue-cli-plugin-coffee
npm ERR!   dev vue-cli-plugin-coffee@"~1.0.0" 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.

[shoffmeister]

Things get further with yarn, but there the same issue is a warning.

git-log--graph/web on  master [!?] is 📦 v0.0.0-see-extension via  v18.18.0 
❯ npx yarn install
yarn install v1.22.19
warning ../../../../../package.json: No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning " > [email protected]" has unmet peer dependency "webpack@^4.0.0 || ^5.0.0".
warning " > [email protected]" has unmet peer dependency "webpack@^5.0.0".
warning " > [email protected]" has incorrect peer dependency "@vue/cli-service@^4.3.1".
warning "vue-cli-plugin-coffee > [email protected]" has unmet peer dependency "webpack@>=2".
warning "vue-cli-plugin-coffee > [email protected]" has unmet peer dependency "webpack@^4.0.0".

[phil294]

hey, sorry for the delay, TBH I have no idea what's causing this. Let me know if you figure it out.

I want to change all the dependencies to something more modern, problem is the coffee-loader depends on old webpack stuff, so perhaps it isn't even really possible