Update dependency expect-type to v0.16.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
expect-type	0.14.2 -> 0.16.0

---

Release Notes

mmkal/expect-type (expect-type)

v0.16.0

Compare Source

What's Changed

• support functions with this parameters by @​mmkal and @​papb in https://github.com/mmkal/expect-type/pull/15
• Prevent the .not modifier from being chained by @​trevorade in https://github.com/mmkal/expect-type/pull/20
• Rewrite Equal to use the equality check from ReadonlyEquivalent exclusively by @​trevorade in https://github.com/mmkal/expect-type/pull/21

Note that #​21 has affected behavior for intersection types, which can result in (arguably) false errors:

// @​ts-expect-error the following line doesn't compile, even though the types are arguably the same.
// See https://github.com/mmkal/expect-type/pull/21
expectTypeOf<{a: 1} & {b: 2}>().toEqualTypeOf<{a: 1; b: 2}>()

Full Changelog: mmkal/expect-type@v0.15.0...v16.0.0

v0.15.0

Compare Source

What's Changed

• Update Extends to not distribute over union types by @​trevorade in https://github.com/mmkal/expect-type/pull/12

New Contributors

• @​trevorade made their first contribution in https://github.com/mmkal/expect-type/pull/12

Full Changelog: mmkal/expect-type@v0.14.2...v0.15.0

---

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 has been generated by Mend Renovate. View repository job log here.

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5175d15

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR