Hey everyone! First of all, sorry for not being as active during the last 1-2 years. I've been quite busy at work and didn't have much time to look into web development. As I now have some more time again, I'll try to dedicate some time and love to this package 🙂
First things first, I'll create a final release for Angular 12 with the current versioning (would be 2.2.4 then), supporting Angular 12-15. The next step will be to create a new release that aligns with the recent developments in the world of Angular (standalone components, mostly, but also the way overdue Ivy support (#144 and #257). This release will support Angular 16 and up.
However, I'm now thinking of how to approach versioning to be better prepared for future version changes of Angular. I've learned by now that it's important to only change the supported Angular version in major releases of the package to not break build systems (sorry) 😄 I'd like to keep supporting at least the 2 previous major Angular versions with this package (as is the convention by the Angular core team), but nevertheless integrate new approaches to Angular development as they appear.
Are there recommended approaches in the Angular world on how to handle this?
I'll close the other issues on version support in favor of this one:
Hey everyone! First of all, sorry for not being as active during the last 1-2 years. I've been quite busy at work and didn't have much time to look into web development. As I now have some more time again, I'll try to dedicate some time and love to this package 🙂
First things first, I'll create a final release for Angular 12 with the current versioning (would be 2.2.4 then), supporting Angular 12-15. The next step will be to create a new release that aligns with the recent developments in the world of Angular (standalone components, mostly, but also the way overdue Ivy support (#144 and #257). This release will support Angular 16 and up.
However, I'm now thinking of how to approach versioning to be better prepared for future version changes of Angular. I've learned by now that it's important to only change the supported Angular version in major releases of the package to not break build systems (sorry) 😄 I'd like to keep supporting at least the 2 previous major Angular versions with this package (as is the convention by the Angular core team), but nevertheless integrate new approaches to Angular development as they appear.
Are there recommended approaches in the Angular world on how to handle this?
I'll close the other issues on version support in favor of this one: