build: bump zone.js from 0.10.3 to 0.11.3

[dependabot]

Bumps zone.js from 0.10.3 to 0.11.3.

Changelog

Sourced from zone.js's changelog.

0.11.3 (2020-10-27)

Bug Fixes

• zone.js: remove global declaration (#37861) (90c0772), closes #37531

0.11.2 (2020-09-19)

Bug Fixes

• zone.js: jest getRealSystemTime should return native time (#39127) (ffc3332)
• zone.js: add missing types field in package.json (#38585) (27cc56b), closes #38584
• zone.js: defineProperty patch should not swallow error (#37582) (45a73dd), closes #37432
• zone.js: run tests in umd format (#37582) (40096be)
• zone.js: should have better backward compatibilities (#38797) (a33d630), closes #38561 #38669
• zone.js: should invoke xhr send task when no response error occurs (#38836) (d92a0dd), closes #38795
• zone.js: zone.js toString patch should check typeof Promise is function (#38350) (18e474f), closes #38361

Features

• zone.js: add jest fakeTimers support (#39016) (82d54fe), closes #38851

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),

... (truncated)

Commits

• 170af07 release: cut the zone.js-0.11.3 release (#39440)
• 3e47b25 docs(zone.js): update release doc (#39442)
• 9891d67 docs(zone.js): Update docs property to disable IntersectionObserver (#39429)
• 90c0772 fix(zone.js): remove global declaration (#37861)
• 6085d2a test(zone.js): add zone.js externs test (#39108)
• a38293d release: cut the zone.js-0.11.2 release to fix several new issues (#39298)
• 497af77 build(zone.js): zone.js should output esm format for fesm2015 bundles (#39203)
• c53f19a refactor(zone.js): rename several internal apis in fake async zone spec (#39127)
• ffc3332 fix(zone.js): jest getRealSystemTime should return native time (#39127)
• b642f0b docs(zone.js): update changelog to add jest useFakeTimers feature (#39126)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[josephperrott]

LGTM

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}