Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Angular 13 support #4178

Closed
6 tasks done
maxokorokov opened this issue Nov 4, 2021 · 32 comments
Closed
6 tasks done

Angular 13 support #4178

maxokorokov opened this issue Nov 4, 2021 · 32 comments

Comments

@maxokorokov
Copy link
Member

maxokorokov commented Nov 4, 2021

Latest releases:

  • ng-bootstrap 10 with Angular 12 and BS 4.5 (Stable)
  • ng-bootstrap 11 with Angular 13 and BS 4.6 → RC.0
  • ng-bootstrap 12 with Angular 13 and BS 5 → Beta.4

Internal issues:

@inexuscore
Copy link

Any idea when Angular 13 will be supported for the Bootstrap 4.x version? We're trying to update to Angular 13 but a few libraries have conflicting peer dependencies. It would be great to bump the versions and target ng 13 if it's not difficult. Thank you very much.

@terencehonles
Copy link
Contributor

@maxokorokov any thoughts on when the move to rxjs 7.4 might happen? This is possible in Angular 13, but rxjs is declared as using ^6.5.5 so I'm not sure if that would be something that would happen in ng-bootstrap 11 or ng-bootstrap 12. I can see what breaks when migrating, but not sure what branch to target and when/if the changes would be merged.

@maxokorokov
Copy link
Member Author

@terencehonles we'll do the same as all Angular packages and have "rxjs": "^6.5.3 || ^7.4.0" in peer deps the next 11 release

@maxokorokov
Copy link
Member Author

maxokorokov commented Nov 10, 2021

@terencehonles several issues we're currently facing:

  • no ngx-build-plus support for Angular 13
  • no angular-eslint support for Angular 13

I should do the 11.0.0-rc.1 release today though to do some more tests on our side (schematics, stackblitzes, etc.)

@terencehonles
Copy link
Contributor

terencehonles commented Nov 10, 2021

  • no angular-eslint support for Angular 13

Do you want to use the prerelease as mentioned in angular-eslint/angular-eslint#780 (comment) ?

I could open a PR for that, but not sure if you'd want to manage that yourself.

@terencehonles
Copy link
Contributor

terencehonles commented Nov 10, 2021

  • no ngx-build-plus support for Angular 13

Also, looking at ngx-build-plus it looks like development has stalled a bit and when looking how it is used in this repo I'm wondering if it makes more sense to just switch to https://github.com/just-jeb/angular-builders/tree/master/packages/custom-webpack. I believe it will provide the same functionality (using the custom webpack config e2e-app/coverage.webpack.js) and it's already updated to Angular 13 (and the Angular team recently asked to move the Bazel builder there just-jeb/angular-builders#1047 and PRd just-jeb/angular-builders#1048 so it's a well known package)

Same comment about opening a PR for that and that could be done on master for Angular 12, I'm not sure where the Angular 11 WIP branch is.

@sysmat
Copy link

sysmat commented Nov 11, 2021

Generating browser application bundles (phase: setup)...Processing legacy "View Engine" libraries:

ng13

@terencehonles
Copy link
Contributor

  • e2e coverage is not working. Looks like issues with coverage-istanbul-reporter → temporarily disabling custom webpack config

I believe this is supposed to be coverage-istanbul-loader? What was the issue? Did you want me to look a little into this? I'm not sure if this is related to:

Changelog 🔗: Support for karma-coverage-instanbul-reporter has been dropped in favor of the official karma coverage plugin karma-coverage.

That's specifically for Karma, but not sure if the support was just dropped because there didn't need to be 2 different packages or if something else changed.

@terencehonles
Copy link
Contributor

  • unit tests for schematics are broken due to externalSchematic calling @angular/localize ESM issues → temporarily disabling

I got with #4183 by pulling in angular/angular#44016. I wasted a bit of time trying to get jasmine to run the test as an ESM, but then I saw the change on Angular's side 😅.

@shendbajgora
Copy link

@maxokorokov
I'm using angular 13, can't wait for 11.0.0-rc.1 release candidate xD.
Is it possible that this is going to happen on this weekend?

@internalsystemerror
Copy link
Contributor

internalsystemerror commented Nov 18, 2021

@angular-eslint/angular-eslint v13 just dropped FYI https://github.com/angular-eslint/angular-eslint/releases/tag/v13.0.0

(EDIT: I thought I'd test this, and now you're faced with eslint-plugin-deprecation not supporting eslint v8 and reading the comments on the waiting PR, it doesn't look good, i.e. abandoned possibly gund/eslint-plugin-deprecation#38)

@internalsystemerror
Copy link
Contributor

internalsystemerror commented Nov 19, 2021

@maxokorokov hopefully to save you some time, I thought I'd upload the results of my testing. master...internalsystemerror:feature/ng13

I've upgraded @angular-eslint/angular-eslint and the associated eslint packages. The deprecation plugin I upgraded to use a fork though I'm not sure if you'd want to use this yourself as I was just testing.

The karma tests pass locally and the only thing outstanding would be linting errors which I'm unsure how you wish to resolve:

Linting "ng-bootstrap"...

/home/ise/projects/ng-bootstrap/ng-bootstrap/src/datepicker/datepicker-navigation-select.ts
  47:13  error  Output bindings, including aliases, should not be named as standard DOM events  @angular-eslint/no-output-native

/home/ise/projects/ng-bootstrap/ng-bootstrap/src/datepicker/datepicker-navigation.ts
  55:13  error  Output bindings, including aliases, should not be named as standard DOM events  @angular-eslint/no-output-native

/home/ise/projects/ng-bootstrap/ng-bootstrap/src/dropdown/dropdown.ts
  172:10  error  Input bindings should not be aliased (https://angular.io/guide/styleguide#style-05-13)  @angular-eslint/no-input-rename

/home/ise/projects/ng-bootstrap/ng-bootstrap/src/modal/modal-window.ts
  63:11  error  Output bindings should not be aliased (https://angular.io/guide/styleguide#style-05-13)  @angular-eslint/no-output-rename

/home/ise/projects/ng-bootstrap/ng-bootstrap/src/typeahead/typeahead-window.ts
  91:11  error  Output bindings should not be aliased (https://angular.io/guide/styleguide#style-05-13)  @angular-eslint/no-output-rename
  91:11  error  Output bindings, including aliases, should not be named as standard DOM events           @angular-eslint/no-output-native

@divdavem
Copy link
Member

For info, I have opened angular/angular-cli#22220 to fix the issue related to code coverage in e2e tests.

@yktoo
Copy link

yktoo commented Nov 29, 2021

Hey guys, do you have any ETA in mind for the 11.0.0 release?

@divdavem
Copy link
Member

divdavem commented Dec 3, 2021

For info, I have opened #4193 to re-enable code coverage in e2e tests (now that angular/cli 13.0.4 is released)

@pantonis
Copy link

pantonis commented Dec 9, 2021

Any update on this. getting errors while trying to install. I used --force to overcome this.

@markwhitfeld
Copy link

FYI, StackBlitz now supports Angular 13:

Great news! Support for Angular 13 has finally rolled out.
...
For the next day or two (until 12 December 2021), there is a possibility of an initial slow down in starting up the dev server or running NGCC (or potentially even timeouts) as the packages repopulate into the cache as they are used, but it should come right after a refresh or two if you do have any issues. Anything else should be reported as a new issue.

Related StackBlitz issue comment: stackblitz/core#1657 (comment)

@fifty56
Copy link

fifty56 commented Dec 10, 2021

could you please let me know if this is fixed or going to be fixed soon:

>npm install @ng-bootstrap/ng-bootstrap@bootstrap5
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: client-app@0.0.0
npm ERR! Found: @angular/compiler@13.0.3
npm ERR! node_modules/@angular/compiler
npm ERR!   @angular/compiler@"~13.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/compiler@"13.1.0" from @angular/localize@13.1.0
npm ERR! node_modules/@angular/localize
npm ERR!   peer @angular/localize@"^13.0.0" from @ng-bootstrap/ng-bootstrap@12.0.0-beta.4
npm ERR!   node_modules/@ng-bootstrap/ng-bootstrap
npm ERR!     @ng-bootstrap/ng-bootstrap@"12.0.0-beta.4" from the root project

@divdavem
Copy link
Member

For info, I have opened #4198 to fix StackBlitz examples now that StackBlitz supports Angular 13.

@gloriousjob
Copy link

v1.3.2 of eslint-plugin-deprecation supports eslint 8, as of v.1.3.0 (yesterday).

@divdavem
Copy link
Member

v1.3.2 of eslint-plugin-deprecation supports eslint 8, as of v.1.3.0 (yesterday).

I have opened #4202 to update @angular-eslint/schematics and eslint-plugin-deprecation.

@terencehonles
Copy link
Contributor

Do we have any more release blockers (other than the open PR #4202)? Looks like @divdavem took care of quite a few things 💪

@fbasso
Copy link
Member

fbasso commented Dec 16, 2021

The new 11.0.0 has been released. Thank you all for your efforts !

@fbasso fbasso closed this as completed Dec 16, 2021
@ETMitch21
Copy link

could you please let me know if this is fixed or going to be fixed soon:

>npm install @ng-bootstrap/ng-bootstrap@bootstrap5
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: client-app@0.0.0
npm ERR! Found: @angular/compiler@13.0.3
npm ERR! node_modules/@angular/compiler
npm ERR!   @angular/compiler@"~13.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/compiler@"13.1.0" from @angular/localize@13.1.0
npm ERR! node_modules/@angular/localize
npm ERR!   peer @angular/localize@"^13.0.0" from @ng-bootstrap/ng-bootstrap@12.0.0-beta.4
npm ERR!   node_modules/@ng-bootstrap/ng-bootstrap
npm ERR!     @ng-bootstrap/ng-bootstrap@"12.0.0-beta.4" from the root project

Did you get a fix for this? I'm experiencing this today as well.

@terencehonles
Copy link
Contributor

@ETMitch21 If you're installing the bootstrap5 branch you should be posting your questions in #3899. You can still tag a user and quote a comment from this issue in that one if you find it might be helpful context.

@adrianord
Copy link

@terencehonles I'm getting the same issues when using version 11

> npm install @ng-bootstrap/ng-bootstrap
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: shopcart@0.0.0
npm ERR! Found: @angular/core@13.2.1
npm ERR! node_modules/@angular/core
npm ERR!   peer @angular/core@"13.2.1" from @angular/animations@13.2.1
npm ERR!   node_modules/@angular/animations
npm ERR!     peerOptional @angular/animations@"13.2.1" from @angular/platform-browser@13.2.1
npm ERR!     node_modules/@angular/platform-browser
npm ERR!       peer @angular/platform-browser@"13.2.1" from @angular/forms@13.2.1
npm ERR!       node_modules/@angular/forms
npm ERR!         @angular/forms@"~13.2.0" from the root project
npm ERR!       3 more (@angular/platform-browser-dynamic, @angular/router, the root project)
npm ERR!     @angular/animations@"~13.2.0" from the root project
npm ERR!   peer @angular/core@"13.2.1" from @angular/common@13.2.1
npm ERR!   node_modules/@angular/common
npm ERR!     peer @angular/common@"13.2.1" from @angular/forms@13.2.1
npm ERR!     node_modules/@angular/forms
npm ERR!       @angular/forms@"~13.2.0" from the root project
npm ERR!     peer @angular/common@"13.2.1" from @angular/platform-browser@13.2.1
npm ERR!     node_modules/@angular/platform-browser
npm ERR!       peer @angular/platform-browser@"13.2.1" from @angular/forms@13.2.1
npm ERR!       node_modules/@angular/forms
npm ERR!         @angular/forms@"~13.2.0" from the root project
npm ERR!       3 more (@angular/platform-browser-dynamic, @angular/router, the root project)
npm ERR!     3 more (@angular/platform-browser-dynamic, @angular/router, the root project)
npm ERR!   5 more (@angular/forms, @angular/platform-browser, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! @ng-bootstrap/ng-bootstrap@"*" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/core@13.2.2
npm ERR! node_modules/@angular/core
npm ERR!   peer @angular/core@"13.2.2" from @angular/forms@13.2.2
npm ERR!   node_modules/@angular/forms
npm ERR!     @angular/forms@"~13.2.0" from the root project
npm ERR!     peer @angular/forms@"^13.0.0" from @ng-bootstrap/ng-bootstrap@11.0.0
npm ERR!     node_modules/@ng-bootstrap/ng-bootstrap
npm ERR!       @ng-bootstrap/ng-bootstrap@"*" from the root project

It seems that the support for angular 13 does not support anything over angular 13.0.x

@internalsystemerror
Copy link
Contributor

It seems that the support for angular 13 does not support anything over angular 13.0.x

@adrianord I've been using this version since it was released with no issues. Currently on Angular 13.2.2. I suggest you open a new issue if you're certain it's an issue with this package.

@Alex3917
Copy link

@adrianord Did you try deleting your package-lock.json and your node_modules folder, and then re-installing your dependencies? I always get those kinds of errors when upgrading Angular unless I do that.

@devoto13
Copy link
Contributor

devoto13 commented Feb 11, 2022

This is a result of a badly designed package manager. See e.g. #3970 (comment) or a billion similar issues.

Use npm i --legacy-peer-deps as a workaround. Or maybe updating NPM to the latest versions can help.

@adrianord
Copy link

adrianord commented Feb 11, 2022

@internalsystemerror @Alex3917 @devoto13 Thanks for the help guys, I was looking for an issue about this, I guess I was just using all the wrong keywords.

This was on a brand new angular project, using nvm install --lts (v16.13.2) and updating npm (8.4.1) just for reference. It does sound like it's most likely an issue with npm like @devoto13 pointed to.

@maxokorokov maxokorokov unpinned this issue Feb 17, 2022
@hpardess
Copy link

hpardess commented Jun 15, 2022

$ npm install --save @ng-bootstrap/ng-bootstrap
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: app-web@0.0.0
npm ERR! Found: @angular/core@13.3.8
npm ERR! node_modules/@angular/core
npm ERR!   peer @angular/core@"13.3.8" from @angular/animations@13.3.8
npm ERR!   node_modules/@angular/animations
npm ERR!     peerOptional @angular/animations@"13.3.8" from @angular/platform-browser@13.3.8
npm ERR!     node_modules/@angular/platform-browser
npm ERR!       peer @angular/platform-browser@"13.3.8" from @angular/forms@13.3.8
npm ERR!       node_modules/@angular/forms
npm ERR!         peer @angular/forms@">=13.0.0 <14.0.0" from @ng-select/ng-select@8.1.1
npm ERR!         node_modules/@ng-select/ng-select
npm ERR!         1 more (the root project)
npm ERR!       4 more (@angular/platform-browser-dynamic, @angular/router, ...)
npm ERR!     @angular/animations@"~13.3.0" from the root project
npm ERR!   peer @angular/core@"13.3.8" from @angular/common@13.3.8
npm ERR!   node_modules/@angular/common
npm ERR!     peer @angular/common@"13.3.8" from @angular/forms@13.3.8
npm ERR!     node_modules/@angular/forms
npm ERR!       peer @angular/forms@">=13.0.0 <14.0.0" from @ng-select/ng-select@8.1.1
npm ERR!       node_modules/@ng-select/ng-select
npm ERR!         @ng-select/ng-select@"^8.1.1" from the root project
npm ERR!       1 more (the root project)
npm ERR!     peer @angular/common@"13.3.8" from @angular/platform-browser@13.3.8
npm ERR!     node_modules/@angular/platform-browser
npm ERR!       peer @angular/platform-browser@"13.3.8" from @angular/forms@13.3.8
npm ERR!       node_modules/@angular/forms
npm ERR!         peer @angular/forms@">=13.0.0 <14.0.0" from @ng-select/ng-select@8.1.1
npm ERR!         node_modules/@ng-select/ng-select
npm ERR!         1 more (the root project)
npm ERR!       4 more (@angular/platform-browser-dynamic, @angular/router, ...)
npm ERR!     6 more (@angular/platform-browser-dynamic, @angular/router, ...)
npm ERR!   8 more (@angular/forms, @angular/platform-browser, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! @ng-bootstrap/ng-bootstrap@"*" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/core@13.3.11
npm ERR! node_modules/@angular/core
npm ERR!   peer @angular/core@"13.3.11" from @angular/forms@13.3.11
npm ERR!   node_modules/@angular/forms
npm ERR!     @angular/forms@"~13.3.0" from the root project
npm ERR!     peer @angular/forms@"^13.0.0" from @ng-bootstrap/ng-bootstrap@12.1.2
npm ERR!     node_modules/@ng-bootstrap/ng-bootstrap
npm ERR!       @ng-bootstrap/ng-bootstrap@"*" 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.

Facing same error with Angular v13.3
npm v8.12.2

@hpardess
Copy link

hpardess commented Jun 23, 2022

$ ng add @ng-bootstrap/ng-bootstrap
ℹ Using package manager: npm
⚠ Unable to find compatible package. Using 'latest' tag.
⚠ Package has unmet peer dependencies. Adding the package may not succeed.

The package @ng-bootstrap/ng-bootstrap@12.1.2 will be installed and executed.
Would you like to proceed? Yes
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: xyz-web@0.0.0
npm ERR! Found: @angular/common@14.0.3
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"^14.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^13.0.0" from @ng-bootstrap/ng-bootstrap@12.1.2
npm ERR! node_modules/@ng-bootstrap/ng-bootstrap
npm ERR!   @ng-bootstrap/ng-bootstrap@"12.1.2" 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! See /Users/xyz/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/xyz/.npm/_logs/2022-06-23T07_55_43_813Z-debug-0.log
✖ Packages installation failed, see above.
0 verbose cli /usr/local/bin/node /usr/local/bin/npm
1 info using npm@8.12.2
2 info using node@v16.13.0
3 timing npm:load:whichnode Completed in 1ms
4 timing config:load:defaults Completed in 1ms
5 timing config:load:file:/usr/local/lib/node_modules/npm/npmrc Completed in 0ms
6 timing config:load:builtin Completed in 1ms
7 timing config:load:cli Completed in 4ms
8 timing config:load:env Completed in 0ms
9 timing config:load:file:/Users/xyz/Documents/xyz-web/.npmrc Completed in 0ms
10 timing config:load:project Completed in 2ms
11 timing config:load:file:/Users/xyz/.npmrc Completed in 2ms
12 timing config:load:user Completed in 2ms
13 timing config:load:file:/usr/local/etc/npmrc Completed in 0ms
14 timing config:load:global Completed in 0ms
15 timing config:load:validate Completed in 0ms
16 timing config:load:credentials Completed in 1ms
17 timing config:load:setEnvs Completed in 1ms
18 timing config:load Completed in 13ms
19 timing npm:load:configload Completed in 13ms
20 timing npm:load:mkdirpcache Completed in 1ms
21 timing npm:load:mkdirplogs Completed in 0ms
22 verbose title npm install @ng-bootstrap/ng-bootstrap@12.1.2
23 verbose argv "install" "@ng-bootstrap/ng-bootstrap@12.1.2"
24 timing npm:load:setTitle Completed in 24ms
25 timing config:load:flatten Completed in 3ms
26 timing npm:load:display Completed in 3ms
27 verbose logfile logs-max:10 dir:/Users/xyz/.npm/_logs
28 verbose logfile /Users/xyz/.npm/_logs/2022-06-23T07_55_43_813Z-debug-0.log
29 timing npm:load:logFile Completed in 7ms
30 timing npm:load:timers Completed in 0ms
31 timing npm:load:configScope Completed in 0ms
32 timing npm:load Completed in 50ms
33 timing arborist:ctor Completed in 1ms
34 silly logfile start cleaning logs, removing 2 files
35 silly logfile done cleaning log files
36 timing idealTree:init Completed in 909ms
37 timing idealTree:userRequests Completed in 4ms
38 silly idealTree buildDeps
39 silly fetch manifest @ng-bootstrap/ng-bootstrap@12.1.2
40 timing arborist:ctor Completed in 0ms
41 http fetch GET 200 https://registry.npmjs.org/@ng-bootstrap%2fng-bootstrap 648ms (cache hit)
42 silly fetch manifest @angular/common@^14.0.0
43 http fetch GET 200 https://registry.npmjs.org/@angular%2fcommon 10ms (cache hit)
44 silly fetch manifest @angular/common@^13.0.0
45 silly fetch manifest @angular/core@^14.0.0
46 http fetch GET 200 https://registry.npmjs.org/@angular%2fcore 10ms (cache hit)
47 silly fetch manifest rxjs@~7.5.0
48 http fetch GET 200 https://registry.npmjs.org/rxjs 7ms (cache hit)
49 silly fetch manifest zone.js@~0.11.4
50 http fetch GET 200 https://registry.npmjs.org/zone.js 9ms (cache hit)
51 timing idealTree Completed in 1637ms
52 timing command:install Completed in 1656ms
53 verbose stack Error: unable to resolve dependency tree
53 verbose stack     at Arborist.[failPeerConflict] (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1428:25)
53 verbose stack     at Arborist.[loadPeerSet] (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1394:34)
53 verbose stack     at async Arborist.[buildDepStep] (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:976:11)
53 verbose stack     at async Arborist.buildIdealTree (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:218:7)
53 verbose stack     at async Promise.all (index 1)
53 verbose stack     at async Arborist.reify (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:153:5)
53 verbose stack     at async Install.exec (/usr/local/lib/node_modules/npm/lib/commands/install.js:156:5)
53 verbose stack     at async module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:78:5)
54 verbose cwd /Users/xyz/Documents/xyz-web
55 verbose Darwin 17.7.0
56 verbose node v16.13.0
57 verbose npm  v8.12.2
58 error code ERESOLVE
59 error ERESOLVE unable to resolve dependency tree
60 error
61 error While resolving: xyz-web@0.0.0
61 error Found: @angular/common@14.0.3
61 error node_modules/@angular/common
61 error   @angular/common@"^14.0.0" from the root project
61 error
61 error Could not resolve dependency:
61 error peer @angular/common@"^13.0.0" from @ng-bootstrap/ng-bootstrap@12.1.2
61 error node_modules/@ng-bootstrap/ng-bootstrap
61 error   @ng-bootstrap/ng-bootstrap@"12.1.2" from the root project
61 error
61 error Fix the upstream dependency conflict, or retry
61 error this command with --force, or --legacy-peer-deps
61 error to accept an incorrect (and potentially broken) dependency resolution.
61 error
61 error See /Users/xyz/.npm/eresolve-report.txt for a full report.
62 verbose exit 1
63 timing npm Completed in 1846ms
64 verbose unfinished npm timer reify 1655970943995
65 verbose unfinished npm timer reify:loadTrees 1655970944010
66 verbose unfinished npm timer idealTree:buildDeps 1655970944924
67 verbose unfinished npm timer idealTree:#root 1655970944925
68 verbose code 1
69 error A complete log of this run can be found in:
69 error     /Users/xyz/.npm/_logs/2022-06-23T07_55_43_813Z-debug-0.log

Facing same error with Angular v14
npm v8.12.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests