[Feature request]: Angular 19-21 support

[paulirwin]

Description

19.0.0-beta.1 is still in beta as a prerelease, and not only has Angular 20 come out since then, but Angular 21 is out now. This project should update to keep up with Angular.

I propose that this project:

• Promote 19.0.0-beta.1 out of beta as 19.0.0, if there are no known blocker issues
• Create a 20.0.0 release targeting Angular 20, for those users that need it
• Create a 21.0.0 release targeting Angular 21

I'd be happy to help with this in any way I can, just let me know. If you'd like, I can get started on an Angular 20 PR.

Problem Statement/Justification

Need this library upgraded to work with newer Angular versions.

Additional Information

Angular 21 release: https://blog.angular.dev/announcing-angular-v21-57946c34f14b

Angular 20 release: https://blog.angular.dev/announcing-angular-v20-b5c9c06cf301

Willing to submit a PR?

Yes

[robertKamrowski]

HI, when consumers can expect an update to v20?

[paulirwin]

@sibiraj-s There is now a PR for Angular 21 support (#637) - although I still believe there is value in having Angular 19 and 20 releases as those are still supported by the Angular team. Can you provide a response to the idea of promoting 19.0.0-beta.1 out of beta? If my plan sounds good, I can do the Angular 20 PR, then we can rebase #637 on all of that.

[paulirwin]

@sibiraj-s As the top (human) contributor to this project after you, I would like to volunteer to be a co-maintainer of this project with you if you are open to that, to help with reviewing PRs, making releases, etc. My employer will sponsor my time. This issue (Angular upgrades) is very important to us, and without having a ngx-editor release since 2024, it is becoming urgent since Angular 18 is already out of support. Additionally, I'd be happy to contribute fixes and other maintenance as well (such as my two open PRs). Please let me know if you are interested in that.

I am going to assume that my plan above makes sense, and regardless of co-maintainer status, I will proceed with preparing Angular 20 (which is still supported until November) and Angular 21 PRs. In my humble opinion, PR #637 (which also upgrades to Angular 21) goes a little too far with adding the zoneless change which makes it a large PR, so that could be rebased on the latter of my upgrade PRs once merged to limit the scope to just zoneless support.