Which @angular/* package(s) are the source of the bug
I wouldn’t call it a bug strictly, but those are the related packages:
@angular/core, zone.js
Is this a regression?
No
Description
Angular 14.0.0 Changelog mentions some changes in zone.js (related to this commit f19b36f), however new version of zone.js was not released yet.
By any chance, do you plan to release new [email protected] (or 0.12.0?) and point it as a peerDependency of angular/[email protected]?
If not, I think we should remove the zone.js changes from Angular 14 changelog.
cc @JiaLiPassion
Please provide a link to a minimal reproduction of the bug
N/A
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run ng version)
Anything else?
I’m not sure if the issue template for bug is appropriate for this issue, but other templates like “feature request” or “docs” didn’t look more appropriate to me.
Which @angular/* package(s) are the source of the bug
I wouldn’t call it a bug strictly, but those are the related packages:
@angular/core, zone.js
Is this a regression?
No
Description
Angular 14.0.0 Changelog mentions some changes in zone.js (related to this commit f19b36f), however new version of zone.js was not released yet.
By any chance, do you plan to release new [email protected] (or 0.12.0?) and point it as a peerDependency of angular/[email protected]?
If not, I think we should remove the zone.js changes from Angular 14 changelog.
cc @JiaLiPassion
Please provide a link to a minimal reproduction of the bug
N/A
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version)Anything else?
I’m not sure if the issue template for bug is appropriate for this issue, but other templates like “feature request” or “docs” didn’t look more appropriate to me.