Update dependency tslib to ^2.6.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
tslib (source)	^2.3.0 -> ^2.6.3

---

Release Notes

Microsoft/tslib (tslib)

v2.6.3

Compare Source

What's Changed

• 'await using' normative changes by @​rbuckton in https://github.com/microsoft/tslib/pull/258

Full Changelog: microsoft/tslib@v2.6.2...v2.6.3

v2.6.2: tslib 2.6.2

Compare Source

What's Changed

• Fix path to exports["module"]["types"] by @​andrewbranch in https://github.com/microsoft/tslib/pull/217

Full Changelog: microsoft/tslib@v2.6.1...v2.6.2

v2.6.1: tslib 2.6.1

Compare Source

What's Changed

• Allow functions as values in __addDisposableResource by @​rbuckton in https://github.com/microsoft/tslib/pull/215
• Stop using es6 syntax in the es6 file by @​andrewbranch in https://github.com/microsoft/tslib/pull/216

Full Changelog: microsoft/tslib@2.6.0...v2.6.1

v2.6.0: tslib 2.6.0

Compare Source

What's Changed

• Add helpers for using and await using by @​rbuckton in https://github.com/microsoft/tslib/pull/213

Full Changelog: microsoft/tslib@v2.5.3...2.6.0

v2.5.3: tslib 2.5.3

Compare Source

What's Changed

• Do not reference tslib.es6.js from package.json exports by @​andrewbranch in https://github.com/microsoft/tslib/pull/208

Full Changelog: microsoft/tslib@2.5.2...v2.5.3

v2.5.2: tslib 2.5.2

Compare Source

This release explicitly re-exports helpers to work around TypeScript's incomplete symbol resolution for tslib.

v2.5.1: tslib 2.5.1

Compare Source

This release of tslib provides fixes for two issues.

First, it reverses the order of init hooks provided by decorators to correctly reflect proposed behavior.

Second, it corrects the exports field of tslib's package.json and provides accurate declaration files so that it may be consumed under the node16 and bundler settings for moduleResolution.

v2.5.0: tslib 2.5.0

Compare Source

What's New

• Fix asyncDelegator reporting done too early by @​apendua in https://github.com/microsoft/tslib/pull/187
• Add support for TypeScript 5.0's __esDecorate and related helpers by @​rbuckton in https://github.com/microsoft/tslib/pull/193

Full Changelog: microsoft/tslib@2.4.1...2.5.0

v2.4.1: tslib 2.4.1

Compare Source

This release contains fixes for early returns and throws invoked on generators.

v2.4.0: tslib 2.4.0

Compare Source

This release includes the __classPrivateFieldIn helper as well as an update to __createBinding to reduce indirection between multiple re-exports.

v2.3.1: tslib 2.3.1

Compare Source

This release updates the __spreadArray helper for TypeScript 4.4 to correctly operate on collections that are not "concat-spreadable" such as the DOM's NodeLists and HTMLCollections.

---

Configuration

📅 Schedule: Branch creation - "after 2am and before 7am every weekday,after 2am and before 7am every weekend" in timezone Asia/Yangon, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @angular-devkit/[email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/compiler-cli
npm ERR!   dev @angular/compiler-cli@"^11.2.14" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/compiler-cli@"^12.0.0 || ^12.1.0-next" from @angular-devkit/[email protected]
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   dev @angular-devkit/build-angular@"12.1.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/[email protected]
npm ERR! node_modules/@angular/compiler-cli
npm ERR!   peer @angular/compiler-cli@"^12.0.0 || ^12.1.0-next" from @angular-devkit/[email protected]
npm ERR!   node_modules/@angular-devkit/build-angular
npm ERR!     dev @angular-devkit/build-angular@"12.1.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/3212a0/7b7ee5/cache/others/npm/_logs/2023-08-18T19_11_32_909Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/3212a0/7b7ee5/cache/others/npm/_logs/2023-08-18T19_11_32_909Z-debug-0.log