Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency zone.js to ~0.15.0 #53

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 22, 2019

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
zone.js (source, changelog) ~0.8.26 -> ~0.15.0 age adoption passing confidence

Release Notes

angular/angular (zone.js)

v0.15.0

Compare Source

Bug Fixes
BREAKING CHANGES
  • zone.js: fakeAsync will now flush pending timers at the end of
    the given function by default. To opt-out of this, you can use {flush: false} in options parameter of fakeAsync

0.14.10 (2024-08-05)

Features
  • zone.js: Add 'flush' parameter option to fakeAsync to flush after the test (#​57137) (99d679d)

0.14.8 (2024-07-17)

Bug Fixes

0.14.7 (2024-06-06)

Bug Fixes

0.14.6 (2024-05-16)

Bug Fixes

0.14.5 (2024-04-30)

Bug Fixes

0.14.4 (2024-02-13)

Bug Fixes

0.14.3 (2023-12-19)

Bug Fixes
Features

0.14.2 (2023-11-03)

Bug Fixes
  • zone.js: disable wrapping unhandled promise error by default (6d7eb35)

14.0.1 (2023-10-25)

Bug Fixes

v0.14.10

Compare Source

Features
  • zone.js: Add 'flush' parameter option to fakeAsync to flush after the test (#​57137) (99d679d)

v0.14.8

Compare Source

Bug Fixes

v0.14.7

Compare Source

Bug Fixes

v0.14.6

Compare Source

Bug Fixes

v0.14.5

Compare Source

Bug Fixes

v0.14.4

Compare Source

Bug Fixes

v0.14.3

Compare Source

Bug Fixes
Features

v0.14.2

Compare Source

Bug Fixes
  • zone.js: disable wrapping unhandled promise error by default (6d7eb35)

v0.14.1

Compare Source

v0.14.0

Compare Source

Features
BREAKING CHANGES
  • zone.js: Deep and legacy dist/ imports like zone.js/bundles/zone-testing.js and zone.js/dist/zone are no longer allowed. zone-testing-bundle and zone-testing-node-bundle are also no longer part of the package.

The proper way to import zone.js and zone.js/testing is:

import 'zone.js';
import 'zone.js/testing';

0.13.3 (2023-09-12)

Bug Fixes

0.13.2 (2023-09-07)

Bug Fixes

v0.13.1 (2023-06-09)

Bug Fixes
Features
Reverts

v0.13.3

Compare Source

Bug Fixes

v0.13.2

Compare Source

Bug Fixes

v0.13.1

Compare Source

Bug Fixes
Features
Reverts

v0.13.0

Compare Source

v0.12.0

Compare Source

Bug Fixes

0.11.8 (2022-08-08)

Features
  • zone.js: Update to the simpler Async Stack Tagging v2 API (#​46958) (f23232f)

0.11.7 (2022-07-20)

Bug Fixes
  • zone.js: do not invoke jasmine done callback multiple times with waitForAsync (4e77c7fbf38)
Features
  • zone.js: add AsyncStackTaggingZoneSpec implementation (#​46693) (848a009)
  • zone.js: include jasmine describe block name when raising unexpected task error (de86285)
  • zone.js: include zone name when sync-test zone reports tasks (72c2567)

0.11.6 (2022-06-02)

Bug Fixes
BREAKING CHANGES
  • zone.js: in TaskTrackingZoneSpec track a periodic task until it is cancelled

The breaking change is scoped only to the plugin
zone.js/plugins/task-tracking. If you used TaskTrackingZoneSpec and
checked the pending macroTasks e.g. using (this.ngZone as any)._inner ._parent._properties.TaskTrackingZone.getTasksFor('macroTask'), then
its behavior slightly changed for periodic macrotasks. For example,
previously the setInterval macrotask was no longer tracked after its
callback 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
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
  • zone.js: refactor(zone.js): rename several internal apis in fake async zone spec (#​39127) (8a68669)
Build
  • zone.js: build(zone.js): zone.js should output esm format for fesm2015 bundles (#​39203) (822b838)
BREAKING CHANGES
  • zone.js: ZoneJS no longer swallows errors produced by 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.

0.11.1 (2020-08-19)

Bug Fixes

v0.11.8

Compare Source

Features
  • zone.js: Update to the simpler Async Stack Tagging v2 API (#​46958) (f23232f)

v0.11.7

Compare Source

Bug Fixes
  • zone.js: do not invoke jasmine done callback multiple times with waitForAsync (4e77c7fbf38)
Features
  • zone.js: add AsyncStackTaggingZoneSpec implementation (#​46693) (848a009)
  • zone.js: include jasmine describe block name when raising unexpected task error (de86285)
  • zone.js: include zone name when sync-test zone reports tasks (72c2567)

v0.11.6

Compare Source

Bug Fixes
BREAKING CHANGES
  • zone.js: in TaskTrackingZoneSpec track a periodic task until it is cancelled

The breaking change is scoped only to the plugin
zone.js/plugins/task-tracking. If you used TaskTrackingZoneSpec and
checked the pending macroTasks e.g. using (this.ngZone as any)._inner ._parent._properties.TaskTrackingZone.getTasksFor('macroTask'), then
its behavior slightly changed for periodic macrotasks. For example,
previously the setInterval macrotask was no longer tracked after its
callback 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
Features

v0.11.4

Compare Source

Bug Fixes
Features

v0.11.3

Compare Source

Bug Fixes

v0.11.2

Bug Fixes
Features
Refactor
  • zone.js: refactor(zone.js): rename several internal apis in fake async zone spec (#​39127) (8a68669)
Build
  • zone.js: build(zone.js): zone.js should output esm format for fesm2015 bundles (#​39203) (822b838)
BREAKING CHANGES
  • zone.js: ZoneJS no longer swallows errors produced by 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 the dist folder.
They were (1) ES5 bundle distributed as zone.js and (2) ES2015 bundle distributed as zone-evergreen.js.
These bundles are used for Angular's differential-loading mechanism.

Prior to v0.11.11 the following code

import 'zone.js';

would load the ES5 bundle from dist/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 match Angular Package Format.
So the same code

import 'zone.js';

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 under dist.
To restore the old behavior change the polyfills.ts generated by Angular CLI to import like so:

import 'zone.js/dist/zone';

v0.11.0

Compare Source

Bug Fixes
Features

0.10.3 (2020-02-27)

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/zone.js-0.x branch from 21b157c to fe5c98f Compare April 7, 2020 17:19
@renovate renovate bot changed the title Update dependency zone.js to ~0.9.0 Update dependency zone.js to ~0.10.0 Apr 7, 2020
@renovate renovate bot force-pushed the renovate/zone.js-0.x branch from fe5c98f to ba99db9 Compare August 23, 2020 06:00
@renovate renovate bot changed the title Update dependency zone.js to ~0.10.0 Update dependency zone.js to ~0.11.0 Aug 23, 2020
@renovate renovate bot force-pushed the renovate/zone.js-0.x branch from ba99db9 to 713b2ed Compare November 20, 2022 08:59
@renovate renovate bot changed the title Update dependency zone.js to ~0.11.0 Update dependency zone.js to ~0.12.0 Nov 20, 2022
@renovate renovate bot force-pushed the renovate/zone.js-0.x branch from 713b2ed to 8f387e9 Compare March 19, 2023 01:59
@renovate renovate bot changed the title Update dependency zone.js to ~0.12.0 Update dependency zone.js to ~0.13.0 Mar 19, 2023
@renovate renovate bot force-pushed the renovate/zone.js-0.x branch from 8f387e9 to 002ec8c Compare September 18, 2023 10:50
@renovate renovate bot changed the title Update dependency zone.js to ~0.13.0 Update dependency zone.js to ~0.14.0 Sep 18, 2023
@renovate renovate bot force-pushed the renovate/zone.js-0.x branch from 002ec8c to 5d16e01 Compare August 21, 2024 21:44
@renovate renovate bot changed the title Update dependency zone.js to ~0.14.0 Update dependency zone.js to ~0.15.0 Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants