angular-inviewport icon indicating copy to clipboard operation
angular-inviewport copied to clipboard

Compatibility with Angular 13

Open elvirusDE opened this issue 3 years ago • 4 comments

Does anyone have this problem? My prod build does not build because of dependency conflicts. It seems to me that the package is not ready for Angular 13.

Log output:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @thisissoon/[email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"~13.3.6" from the root project
npm ERR!   peer @angular/core@"13.3.6" from @angular/[email protected]
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"~13.3.6" from the root project
npm ERR!     peer @angular/animations@"^13.0.0 || ^14.0.0-0" from @angular/[email protected]
npm ERR!     node_modules/@angular/material
npm ERR!       @angular/material@"^13.3.6" from the root project
npm ERR!     1 more (@angular/platform-browser)
npm ERR!   10 more (@angular/cdk, @angular/common, @angular/flex-layout, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@">=5.0.0 <9.0.0" from @thisissoon/[email protected]
npm ERR! node_modules/@thisissoon/angular-inviewport
npm ERR!   @thisissoon/angular-inviewport@"^4.2.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   peer @angular/core@">=5.0.0 <9.0.0" from @thisissoon/[email protected]
npm ERR!   node_modules/@thisissoon/angular-inviewport
npm ERR!     @thisissoon/angular-inviewport@"^4.2.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 /tmp/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/.npm/_logs/2022-06-14T08_02_56_177Z-debug-0.log

What can I do to get my project build again? Any ideas?

elvirusDE avatar Jun 14 '22 08:06 elvirusDE

Your assumption is correct, this package hasn't been tested with Angular 13 as we aren't actively developing it anymore. Happy to accept PR's if you find a fix.

andypwarren avatar Jun 14 '22 08:06 andypwarren

Ok, thank you for your reply.

  1. Is there any replacement available because unfortunately I am dependent on this package...
  2. There are a lot of open PRs in the project. If I update the dependencies, would you incorporate my PR or am I supposed to fork the project in order to continue?

elvirusDE avatar Jun 14 '22 08:06 elvirusDE

  1. I'm not sure I haven't looked into this for a while.
  2. I'd suggest forking it, making the changes and then submitting an MR

andypwarren avatar Jun 14 '22 08:06 andypwarren

I made a pull request for the update. It is compatible with Angular 14. I also have published my fork as @elvirus/angular-inviewport and tested it with my application and it is working as expected.

elvirusDE avatar Jun 15 '22 01:06 elvirusDE