Skip to content

ERESOLVE unable to resolve dependency tree with Angular 16.0.2 #151

@melroy89

Description

@melroy89

Describe the bug

Issue with npm dependencies after executing ng add @briebug/jest-schematic.
Yes, I could use the --legacy-peer-deps parameter, but that is a workaround. Please fix upstream.

npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: erp.js@0.1.0
npm ERR! Found: @angular-devkit/build-angular@16.0.2
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   dev @angular-devkit/build-angular@"^16.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular-devkit/build-angular@"^15.0.0" from @angular-builders/jest@15.0.0
npm ERR! node_modules/@angular-builders/jest
npm ERR!   dev @angular-builders/jest@"15.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.

To Reproduce
Steps to reproduce the behavior:

  1. ng add @briebug/jest-schematic

Expected behavior

No errors.

Screenshots

image

Desktop (please complete the following information):

  • OS: Linux
  • Node version: 18.16.0
  • App type: Angular CLI,
Angular CLI: 16.0.2
Node: 18.16.0
Package Manager: npm 9.5.1
OS: linux x64

Angular: 16.0.2
... animations, cli, common, compiler, compiler-cli, core, forms
... localize, platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1600.2
@angular-devkit/build-angular   16.0.2
@angular-devkit/core            16.0.2
@angular-devkit/schematics      16.0.2
@angular/cdk                    16.0.1
@angular/flex-layout            15.0.0-beta.42
@angular/material               16.0.1
@schematics/angular             16.0.2
rxjs                            7.8.1
typescript                      5.0.4

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions