chore(deps): update dependency tslib to v2.6.2

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
tslib (source)	2.5.2 -> 2.6.2

---

Release Notes

Microsoft/tslib (tslib)

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: https://github.com/microsoft/tslib/compare/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: https://github.com/microsoft/tslib/compare/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: https://github.com/microsoft/tslib/compare/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: https://github.com/microsoft/tslib/compare/2.5.2...v2.5.3

---

Configuration

📅 Schedule: Branch creation - "every month" (UTC), 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 has been generated by Mend Renovate. View repository job log here.

[pull-request-quantifier-deprecated[bot]]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.