[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.

[ghosh81]

@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.

I want to migrate our Angular v18 application to v19 first, but not able to do it because of unavalability of ngx-editor's suitable version! Please help us.

[ghosh81]

@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.

When we can expect the release of ngx-editor v19? It is still in beta version. @paulirwin , @sibiraj-s

[paulirwin]

@ghosh81 I am not a maintainer of this project, so I cannot say when it will be released. But you can check out my company's fork where we have experimental features that have not yet been merged upstream, including releases for Angular 19, 20, and 21: https://www.npmjs.com/package/@feature23/ngx-editor?activeTab=readme

Note that for this to work properly, you have to alias our fork in your package.json like this (replace 21 with whatever version you want between 19-21):

"ngx-editor": "npm:@feature23/ngx-editor@^21.0.0"

To clarify, @feature23/ngx-editor is an unofficial, experimental fork. We are doing this in the open and commit to make available all of our changes upstream to this project. Right now, our fork consists of PR #643 for Angular 20 support in our version 20.0.0, and we have a stacked PR on my personal fork (here) for Angular 21 support in our version 21.0.0, to be submitted here once/if #643 is merged. We might also add some open PRs like #641 and #642 soon if unmerged here, but I do not plan on backporting those to 19 or 20 (all new development will be 21+). We also will upgrade to Angular 22 once it comes out soon, if needed.

Our hope is that these changes will be merged, making our fork just for truly experimental changes. And I still volunteer to help be a maintainer of ngx-editor if the project will have me.

[duncan-sqeptech]

@paulirwin @ghosh81 @sibiraj-s
This has been done and forked and is actively maintained here ngx-editor
Seems like we're duplicating the effort and as this hasn't been touched in over a year by the original maintainer then it's probably fair to assume this isn't going to change anytime soon.

[paulirwin]

@duncan-sqeptech Agreed, this project appears to be currently unmaintained. Which is unfortunate. @sibiraj-s We all hope you're okay!

The other fork you reference does not have Angular 20 support as an intermediate step, and it includes a very large change to adopt zoneless, which is not required to upgrade to Angular 21, and is a bit more for the community to review (which hasn't been done yet; admittedly I haven't fully reviewed it either). I also expressed in my open PR that I believe that Angular version upgrades should be merged independently of big changes like zoneless support. My organization decided that we would rather maintain our own fork (as some of our products depend on it), than risk this happening again. Also, this let us provide an intermediate Angular 20 upgrade step.

I'm not going to try to pitch people on using our fork versus the other one; use whichever one works best for you. But that's the downside of forks, right? It splinters the community. Ideally, these changes would be merged upstream and the project would be actively maintained. Hopefully that will happen soon and our forks can converge again on upstream.

I will say though, in the event that this project doesn't come back to life, that the company I work for – which has been around for nearly two decades and has over 25 people – is prepared to stand behind our fork, keep it open, and continue to make available our changes upstream.