Still kind of new to everything so sorry if this is remedial but can anyone point me in the right direction on resolving these npm issues
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @vue/cli-plugin-eslint@5.0.8
npm ERR! Found: eslint@6.8.0
npm ERR! node_modules/eslint
npm ERR! dev eslint@"^6.7.2" from the root project
npm ERR! peer eslint@"^5.0.0 || ^6.0.0" from @typescript-eslint/eslint-plugin@2.34.0
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR! dev @typescript-eslint/eslint-plugin@"^2.33.0" from the root project
npm ERR! peer @typescript-eslint/eslint-plugin@"^2.7.0" from @vue/eslint-config-typescript@5.1.0
npm ERR! node_modules/@vue/eslint-config-typescript
npm ERR! dev @vue/eslint-config-typescript@"^5.0.2" from the root project
npm ERR! 10 more (@typescript-eslint/experimental-utils, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@">=7.5.0" from @vue/cli-plugin-eslint@5.0.8
npm ERR! node_modules/@vue/cli-plugin-eslint
npm ERR! dev @vue/cli-plugin-eslint@"^5.0.8" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: eslint@8.30.0
npm ERR! node_modules/eslint
npm ERR! peer eslint@">=7.5.0" from @vue/cli-plugin-eslint@5.0.8
npm ERR! node_modules/@vue/cli-plugin-eslint
npm ERR! dev @vue/cli-plugin-eslint@"^5.0.8" 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!
- MMatt Frisbie @mattfriz
As a short term fix, try using the --force flag. I'll look into resolving these dependencies.
- AAustin Barnett @austinb
matt you deserve some sort of award for response time, I've attempted cache clearing the --force flag and the legacy flag. I'm recording each step in hopes of creating a walkthrough for the less coding inclined people.
- MMatt Frisbie @mattfriz
I've been dragging my feet on this for awhile. I'll fix these dependencies and push a fix.
- MIn reply toaustinb⬆:Matt Frisbie @mattfriz
Alright let's try this again. I've updated the master branch with what should be a resolved dependency set.
CircleCI was able to build and run tests with no issues:
https://app.circleci.com/pipelines/github/msfrisbie/track-trace-tools/86/workflows/273373df-0d53-4377-b434-0aaeff41558bI'm switching over to using yarn, I recommend doing the same.
- AAustin Barnett @austinb
should I fork the original Repo
error Command failed.
Exit code: 128
Command: git
Arguments: ls-remote --tags --heads ssh://git@github.com/awardx/vue-extension-mv3-hot-reload.git
Directory: /Users/austinbarnett/track-trace-tools
Output:
Host key verification failed.
fatal: Could not read from remote repository. - In reply tomattfriz⬆:AAustin Barnett @austinb
deleted ran standard and then with the ignore flag and its all good
- Progresswith handling this problem
- AAustin Barnett @austinb
Everything is working. If you get bored I'd gladly donate money for a quick tutorial on changing settings.
- MMatt Frisbie @mattfriz
Happy to assist, reach out at tracktracetools@gmail.com.
I also do contract work to add on custom features.