After upgrading Angular to version 17 using npm --force, my application was running smoothly in a local environment. However, when attempting to deploy it (via octopus deploy), the npm install process was automatically triggered by .Net, resulting in a list of conflicts that halted the execution. I tried replacing the command npm install with npm install --force, but unfortunately, this did not resolve the issue.
I am seeking guidance on how to resolve these types of conflicts or if anyone can share relevant documentation, please?
If anyone knows how to fix the conflict below, I would greatly appreciate your assistance:
# npm resolution error report
While resolving: @angular-eslint/<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="1775627e7b73726557262039233927">[email protected]</a>
Found: <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="b4d1c7d8dddac0f48d9a869a84">[email protected]</a>
node_modules/eslint
dev eslint@"^9.2.0" from the root project
peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="0d687e6164637920787964617e4d392339233d">[email protected]</a>
node_modules/@eslint-community/eslint-utils
@eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="d3a6a7babfa093e4fdebfde3">[email protected]</a>
node_modules/@angular-eslint/eslint-plugin/node_modules/@typescript-eslint/utils
@typescript-eslint/utils@"7.8.0" from @angular-eslint/<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="9bfee8f7f2f5efb6ebf7eefcf2f5dbaaacb5afb5ab">[email protected]</a>
...
Could not resolve dependency:
peer eslint@"^7.20.0 || ^8.0.0" from @angular-eslint/<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="3351465a5f5756417302041d071d03">[email protected]</a>
node_modules/@angular-eslint/builder
dev @angular-eslint/builder@"17.4.0" from the root project
Conflicting peer dependency: <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="d7b2a4bbbeb9a397eff9e2e0f9e7">[email protected]</a>
node_modules/eslint
peer eslint@"^7.20.0 || ^8.0.0" from @angular-eslint/<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="583a2d31343c3d2a18696f766c7668">[email protected]</a>
node_modules/@angular-eslint/builder
dev @angular-eslint/builder@"17.4.0" from the root project
Fixing the upstream dependency conflict is necessary, or reattempt the command with --force or --legacy-peer-deps to potentially accept an incorrect and broken dependency resolution.Here is package.json for reference:
"dependencies": {
...
},
"devDependencies": {
...
}
}