I think you have to ask @hoebbelsB.

I don't own / can't maintain this repo.

Besides and not speaking for rx-angular here:

Personally, I decided in July when I posted here, to phase out rx-angular from our project. Overall the "new" Angular signal based world makes rx-angular obsolete anyway if you ask me. Except you have a really crazy use case. But, than maybe also that should be questioned.

Depends on what you use from rx-angular. But, with AI you can pretty easy migrate. E.g. rxLet / rxIf / rxFor => @let, @if, @for in combination with toSignal to turn you current observables into signals. You can improve further based on that, remove more and more rxjs stuff (which I'd recomment if I were a consultant), use e.g. httpResource instead of http.get. We have/had a quite complex project & everthing got easier following this path. Also, less dependencies is also better since you are less blocked with updates :)

If you use rxState, migration gets a bit more involved. But, also AI will help you with that. Depending on code, it might be a simple signal (target this if you ask me) or you might need some custom code together with e.g. BehaviorSubject to replicate the exact behaviour (in one case I had to do this).

Uh oh!

Angular 22 support #1911

Description

Problem Solved By The Feature

Solution

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions