This repository has been archived by the owner on Aug 16, 2022. It is now read-only.
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:
0.10.3
->0.11.6
Release Notes
angular/angular
v0.11.6
Compare Source
Bug Fixes
process
is defined when patching theGlobalErrors.install
(#45392) (c7bcc1b), closes #42260Symbol.species
safely (#45369) (e2eaac3)BREAKING CHANGES
The breaking change is scoped only to the plugin
zone.js/plugins/task-tracking
. If you usedTaskTrackingZoneSpec
andchecked 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
setInterval
macrotask 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.5
Compare Source
Bug Fixes
done()
multiple times (#45025) (d5565cc)Features
v0.11.4
Compare Source
Bug Fixes
Features
v0.11.3
Compare Source
Bug Fixes
v0.11.2
Bug Fixes
Features
Refactor
Build
BREAKING CHANGES
Object.defineProperty
calls.Prior to this change, ZoneJS monkey patched
Object.defineProperty
and 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.1
Prior to
v0.11.1
, Zone.js provided two distribution bundle formats in thedist
folder.They were (1)
ES5
bundle distributed aszone.js
and (2)ES2015
bundle distributed aszone-evergreen.js
.These bundles are used for Angular's differential-loading mechanism.
Prior to
v0.11.11
the following codewould load the
ES5
bundle 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
ES2015
bundle instead.This is a breaking change for legacy browsers such as
IE11
.For backwards compatibility
zone.js
continues to distribute the same bundles underdist
.To restore the old behavior change the
polyfills.ts
generated byAngular CLI
to import like so:v0.11.0
Compare Source
Bug Fixes
[@types](https://togithub.com/types)/jasmine
to the test cases (#34625) (41667de)Features
0.10.3 (2020-02-27)
Bug Fixes
zone-patch-rxjs
bundle to refer torxjs
(rather than include) it. (#35983) (99ea5d7), closes #35878EventTarget
methods optional inzone.js
extension API (#35954) (5463462)Features
Performance Improvements
0.10.2 (2019-08-13)
Features
0.10.1 (2019-08-02)
Bug Fixes
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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.