Update angular monorepo #2
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
9.0.2->9.1.139.0.2->9.1.139.0.2->9.1.13~0.10.2->~0.13.0Release Notes
angular/angular (@angular/compiler)
v9.1.13Compare Source
v9.1.12Compare Source
v9.1.11Compare Source
v9.1.10Compare Source
v9.1.9Compare Source
v9.1.8Compare Source
v9.1.7Compare Source
v9.1.6Compare Source
v9.1.5Compare Source
v9.1.4Compare Source
v9.1.3Compare Source
v9.1.2Compare Source
v9.1.1Compare Source
v9.1.0Compare Source
v9.0.7Compare Source
v9.0.6Compare Source
v9.0.5Compare Source
v9.0.4Compare Source
v9.0.3Compare Source
angular/angular (@angular/compiler-cli)
v9.1.13Compare Source
v9.1.12Compare Source
v9.1.11Compare Source
v9.1.10Compare Source
v9.1.9Compare Source
v9.1.8Compare Source
v9.1.7Compare Source
v9.1.6Compare Source
v9.1.5Compare Source
v9.1.4Compare Source
v9.1.3Compare Source
v9.1.2Compare Source
v9.1.1Compare Source
v9.1.0Compare Source
v9.0.7Compare Source
v9.0.6Compare Source
v9.0.5Compare Source
v9.0.4Compare Source
v9.0.3Compare Source
angular/angular (@angular/language-service)
v9.1.13Compare Source
v9.1.12Compare Source
v9.1.11Compare Source
v9.1.10Compare Source
v9.1.9Compare Source
v9.1.8Compare Source
v9.1.7Compare Source
v9.1.6Compare Source
v9.1.5Compare Source
v9.1.4Compare Source
v9.1.3Compare Source
v9.1.2Compare Source
v9.1.1Compare Source
v9.1.0Compare Source
v9.0.7Compare Source
v9.0.6Compare Source
v9.0.5Compare Source
v9.0.4Compare Source
v9.0.3Compare Source
angular/angular (zone.js)
v0.13.0Compare Source
v0.12.0Compare Source
Bug Fixes
0.11.8 (2022-08-08)
Features
0.11.7 (2022-07-20)
Bug Fixes
waitForAsync(4e77c7fbf38)Features
describeblock name when raising unexpected task error (de86285)0.11.6 (2022-06-02)
Bug Fixes
processis defined when patching theGlobalErrors.install(#45392) (c7bcc1b), closes #42260Symbol.speciessafely (#45369) (e2eaac3)BREAKING CHANGES
The breaking change is scoped only to the plugin
zone.js/plugins/task-tracking. If you usedTaskTrackingZoneSpecandchecked the pending macroTasks e.g. using
(this.ngZone as any)._inner ._parent._properties.TaskTrackingZone.getTasksFor('macroTask'), thenits behavior slightly changed for periodic macrotasks. For example,
previously the
setIntervalmacrotask was no longer tracked after itscallback was executed for the first time. Now it's tracked until
the task is explicitly cancelled, e.g with
clearInterval(id).0.11.5 (2022-03-03)
Bug Fixes
done()multiple times (#45025) (d5565cc)Features
0.11.4 (2021-02-10)
Bug Fixes
Features
0.11.3 (2020-10-27)
Bug Fixes
0.11.2 (2020-09-19)
Bug Fixes
Features
Refactor
Build
BREAKING CHANGES
Object.definePropertycalls.Prior to this change, ZoneJS monkey patched
Object.definePropertyand if there is an error(such as the property is not configurable or not writable) the patched logic swallowed it
and only console.log was produced. This behavior used to hide real errors,
so the logic is now updated to trigger original errors (if any). One exception
where the patch remains in place is
document.registerElement(to allow smooth transition for code/polyfills that rely on old behavior in legacy browsers).
If your code relies on the old behavior (where errors were not thrown before),
you may need to update the logic to handle the errors that are no longer masked by ZoneJS patch.
0.11.1 (2020-08-19)
Bug Fixes
v0.11.8Compare Source
Features
v0.11.7Compare Source
Bug Fixes
waitForAsync(4e77c7fbf38)Features
describeblock name when raising unexpected task error (de86285)v0.11.6Compare Source
Bug Fixes
processis defined when patching theGlobalErrors.install(#45392) (c7bcc1b), closes #42260Symbol.speciessafely (#45369) (e2eaac3)BREAKING CHANGES
The breaking change is scoped only to the plugin
zone.js/plugins/task-tracking. If you usedTaskTrackingZoneSpecandchecked the pending macroTasks e.g. using
(this.ngZone as any)._inner ._parent._properties.TaskTrackingZone.getTasksFor('macroTask'), thenits behavior slightly changed for periodic macrotasks. For example,
previously the
setIntervalmacrotask was no longer tracked after itscallback was executed for the first time. Now it's tracked until
the task is explicitly cancelled, e.g with
clearInterval(id).v0.11.5Compare Source
Bug Fixes
done()multiple times (#45025) (d5565cc)Features
v0.11.4Compare Source
Bug Fixes
Features
v0.11.3Compare Source
Bug Fixes
v0.11.2Bug Fixes
Features
Refactor
Build
BREAKING CHANGES
Object.definePropertycalls.Prior to this change, ZoneJS monkey patched
Object.definePropertyand if there is an error(such as the property is not configurable or not writable) the patched logic swallowed it
and only console.log was produced. This behavior used to hide real errors,
so the logic is now updated to trigger original errors (if any). One exception
where the patch remains in place is
document.registerElement(to allow smooth transition for code/polyfills that rely on old behavior in legacy browsers).
If your code relies on the old behavior (where errors were not thrown before),
you may need to update the logic to handle the errors that are no longer masked by ZoneJS patch.
v0.11.1Prior to
v0.11.1, Zone.js provided two distribution bundle formats in thedistfolder.They were (1)
ES5bundle distributed aszone.jsand (2)ES2015bundle distributed aszone-evergreen.js.These bundles are used for Angular's differential-loading mechanism.
Prior to
v0.11.11the following codewould load the
ES5bundle fromdist/zone.js.Starting with
v0.11.1, Zone.js follows the Angular Package Format, so the folder structure of the Zone.js bundles is updated to matchAngular Package Format.So the same code
now loads the
ES2015bundle instead.This is a breaking change for legacy browsers such as
IE11.For backwards compatibility
zone.jscontinues to distribute the same bundles underdist.To restore the old behavior change the
polyfills.tsgenerated byAngular CLIto import like so:v0.11.0Compare Source
Bug Fixes
[@types](https://togithub.com/types)/jasmineto the test cases (#34625) (41667de)Features
0.10.3 (2020-02-27)
Bug Fixes
zone-patch-rxjsbundle to refer torxjs(rather than include) it. (#35983) (99ea5d7), closes #35878EventTargetmethods optional inzone.jsextension API (#35954) (5463462)Features
Performance Improvements
0.10.2 (2019-08-13)
Features
0.10.1 (2019-08-02)
Bug Fixes
v0.10.3Compare Source
Bug Fixes
zone-patch-rxjsbundle to refer torxjs(rather than include) it. (#35983) (99ea5d7), closes #35878EventTargetmethods optional inzone.jsextension API (#35954) (5463462)Features
Performance Improvements
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.