Add support for Angular 18

[pitang-teste]

Now that Angular 18 has been released, are there any plans to release a new version that supports Angular 18?

I got this error message:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: ngx-loading@17.0.0
npm ERR! Found: @angular/common@18.0.0
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"^18.0.0" from the root project
npm ERR!   peer @angular/common@"^18.0.0 || ^19.0.0" from @angular/cdk@18.0.0
npm ERR!   node_modules/@angular/cdk
npm ERR!     @angular/cdk@"^18.0.0" from the root project
npm ERR!     peer @angular/cdk@"18.0.0" from @angular/material@18.0.0
npm ERR!     node_modules/@angular/material
npm ERR!       @angular/material@"^18.0.0" from the root project
npm ERR!       1 more (@angular/material-moment-adapter)
npm ERR!   6 more (@angular/forms, @angular/material, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^17.0.0" from ngx-loading@17.0.0
npm ERR! node_modules/ngx-loading
npm ERR!   ngx-loading@"^17.0.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @angular/common@17.3.10
npm ERR! node_modules/@angular/common
npm ERR!   peer @angular/common@"^17.0.0" from ngx-loading@17.0.0
npm ERR!   node_modules/ngx-loading
npm ERR!     ngx-loading@"^17.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.

[mukulghade]

In the meantime, is there any work around?

[Epsilon02]

The author seems rather inactive, so I took action and made a fork of this tool, upgraded it to angular 18 and called it ngx-loading-reloaded.
I hope the original author will come back but in the meantime I will maintain the angular versions to prevent this error messages and would review PRs if some appear.
Maybe i will have more time and motivation to work on it in the future and make improvements if necessary.

[tiago-ilha]

The author seems rather inactive, so I took action and made a fork of this tool, upgraded it to angular 18 and called it ngx-loading-reloaded. I hope the original author will come back but in the meantime I will maintain the angular versions to prevent this error messages and would review PRs if some appear. Maybe i will have more time and motivation to work on it in the future and make improvements if necessary.

Are there any significant differences between versions 17 and 18? Or are there only updates to the base libraries?

[Epsilon02]

The author seems rather inactive, so I took action and made a fork of this tool, upgraded it to angular 18 and called it ngx-loading-reloaded. I hope the original author will come back but in the meantime I will maintain the angular versions to prevent this error messages and would review PRs if some appear. Maybe i will have more time and motivation to work on it in the future and make improvements if necessary.

Are there any significant differences between versions 17 and 18? Or are there only updates to the base libraries?

No nothing new. Just an update because I use this library at work. As I stated in my last comment, I will try to keep it up to date with the current Angular version.
As I see right now Angular 19 is out, so I will try to upgrade to the latest version as soon as I have time for it (hopefully at some point in the next 2 weeks).
If anyone want to take my fork and add new features, they are welcome. Currently it is more like "maintenance mode".

[ArthurDrevot]

Hello, I've created a merge request for a migration to Angular 19, but it is awaiting a reviewer.

#187