scottyaslan commented on PR #9072: URL: https://github.com/apache/nifi/pull/9072#issuecomment-2223528643
> Here is the particular error, which appears to be related to some conflicting dependency versions: > > ``` > [INFO] > [email protected] ci > [INFO] > npm ci --ignore-scripts > [INFO] > [INFO] npm error code ERESOLVE > [INFO] npm error ERESOLVE could not resolve > [INFO] npm error > [INFO] npm error While resolving: @angular-eslint/[email protected] > [INFO] npm error Found: @angular/[email protected] > [INFO] npm error node_modules/@angular/cli > [INFO] npm error dev @angular/cli@"~18.0.0" from the root project > [INFO] npm error > [INFO] npm error Could not resolve dependency: > [INFO] npm error peer @angular/cli@">= 17.0.0 < 18.0.0" from @angular-eslint/[email protected] > [INFO] npm error node_modules/@angular-eslint/schematics > [INFO] npm error dev @angular-eslint/schematics@"17.2.1" from the root project > [INFO] npm error > [INFO] npm error Conflicting peer dependency: @angular/[email protected] > [INFO] npm error node_modules/@angular/cli > [INFO] npm error peer @angular/cli@">= 17.0.0 < 18.0.0" from @angular-eslint/[email protected] > [INFO] npm error node_modules/@angular-eslint/schematics > [INFO] npm error dev @angular-eslint/schematics@"17.2.1" from the root project > [INFO] npm error > [INFO] npm error Fix the upstream dependency conflict, or retry > [INFO] npm error this command with --force or --legacy-peer-deps > [INFO] npm error to accept an incorrect (and potentially broken) dependency resolution. > ``` Thanks @exceptionfactory! This was my first attempt at upgrading the dependencies of our Nx monorepository using their tools to do so and while I did find them helpful it didn't solve all the upgrade issues. I think I have them all sorted now but I will continue babysitting this build until it is green. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
