Angular Updates

[cmckni3]

Creating an issue to collect all Angular support updates and issues for tracking

Angular 14

• Publish to npm

Issue(s): #452 #477
PR: #481

Angular 15

• Publish to npm

Issue(s): #501
PR: #537

Angular 16

• Publish to npm

Issue(s): #495
PR: #545

Angular 17

• Publish to npm

Issue(s): N/A
PR: #550

Angular 18

• In progress

Issue(s): #518
PR: #552

Angular 19

• Pending updates

Issue(s): #522

Angular 20

• Pending updates

Issue(s): #567

[songokudbz]

Hi @cmckni3 do we have a timeline for each Angular version?

[cmckni3]

14.0.0 released

[cmckni3]

Tried to publish 13.0.0 for Angular 13 but Angular 14 complains with #447

[songokudbz]

@cmckni3 a win for humanity with the v14 release! Let's continue up to Angular 19!

[cmckni3]

@cmckni3 a win for humanity with the v14 release! Let's continue up to Angular 19!

Yep. Working on 15

[cmckni3]

13 released and previous version 3.2.0 deprecated.

Published v15 beta

[cmckni3]

Published v15 beta

According to Angular's versioning policy, v15 libraries should work on v16 and v17 as well (previous 2 versions policy).

[cmckni3]

15.0.0 published

16.0.0-beta.3 published

[cmckni3]

16.0.0 published

[khIsm]

Hi @cmckni3

Could you please provide an approximate release date for Angular 19?

Thank you

[songokudbz]

@khIsm you can use the v16.0.0 for Angular 19 until the v19.0.0 is out. The v15 and 16 allows installation for all angular versions above 15 and 16 respectively.

[cmckni3]

Hi @cmckni3

Could you please provide an approximate release date for Angular 19?

Thank you

I am targeting Angular 19 within the next week. I am currently working on Angular 17.

Thanks to @songokudbz for pointing out that I changed the package.json to >= for the v15.0.0 and v16.0.0 releases. I implicitly mentioned this in a previous comment but didn't explicitly call out the version constraint change.

v16.0.0 may work, as @songokudbz pointed out; however, Angular does not guarantee this. When I publish v17.0.0, it should work according to Angular's compatibility policy, as mentioned in my comment. The only issue I encountered with Angular 19 was a compiler error stating the component is not a standalone component.

[songokudbz]

@cmckni3 can be easily fixed.
Mark it to "standalone: false" here, until you migrate to standalone:

@Component({ selector: 'NAME_SELECTOR', templateUrl: './NAME.html', styleUrls: ['./NAME.component.css'], standalone: false })

[cmckni3]

@cmckni3 can be easily fixed. Mark it to "standalone: false" here, until you migrate to standalone:

@Component({ selector: 'NAME_SELECTOR', templateUrl: './NAME.html', styleUrls: ['./NAME.component.css'], standalone: false })

@songokudbz, yeah, I haven't gotten to Angular 19 yet. I thought about making the fix in a branch, but I still wouldn't want to publish it yet. I could publish a beta, but meh.