chore(devDep): Bump typescript from ~4.8.4 to ~5.0.4

[MajorLift]

Motivation

As part of its OKRs (Q2 2024 O3KR4, Q3 2024 O2KR4) the Wallet Framework Team has upgraded all core packages to use TypeScript v5.0, and is enabling other packages throughout our codebase to upgrade as well. Unblocking the snaps monorepo is a high priority, as it has close interdependencies with core monorepo.

This commit upgrades the TypeScript version used in the snaps monorepo by two major versions: v4.9 and v5.0.

• https://devblogs.microsoft.com/typescript/announcing-typescript-4-9/
• https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/

Features

v4.9

• satisfies operator
  • See Improve type safety by applying satisfies operator core#1972
• Unlisted property narrowing with in operator

v5.0

• const Type Parameters:
  • Causes as const inference by default.
  • 77 as const instances in the snaps monorepo.

type HasNames = { names: readonly string[] };
function getNamesExactly<const T extends HasNames>(arg: T): T["names"] {
//                       ^^^^^
    return arg.names;
}
// Inferred type without `const`: string[]
// Inferred type with `const`: readonly ["Alice", "Bob", "Eve"]
// Note: Didn't need to write 'as const' here
const names = getNamesExactly({ names: ["Alice", "Bob", "Eve"] });

• enum improvements:
  • All enums are union enums
  • enum overhaul
  • 30 enum instances in the snaps monorepo.
• Decorators

Breaking Changes

v5.0

• Full list of breaking changes and deprecations: https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#breaking-changes-and-deprecations
• Regressions in Snaps repo
  • Forbidden Implicit Coercions in Relational Operators
    • Fixed here: fffe4b2

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/typescript@5.0.4	None	0	39.2 MB	typescript-bot

🚮 Removed packages: npm/typescript@4.8.4

View full report↗︎

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 94.00%. Comparing base (3ec6169) to head (077b015).

Files	Patch %	Lines
...lator/src/features/builder/components/BaseNode.tsx	0.00%	2 Missing ⚠️
...lator/src/features/builder/components/NodeTree.tsx	0.00%	2 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2594   +/-   ##
=======================================
  Coverage   94.00%   94.00%           
=======================================
  Files         459      459           
  Lines        9650     9650           
  Branches     1482     1482           
=======================================
  Hits         9071     9071           
  Misses        579      579           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[MajorLift]

RE codecov: It looks like there are no tests written for the BaseNode and NodeTree components. Would I be correct in assuming that the codecov warning can be safely ignored?

[Mrtenz]

Would I be correct in assuming that the codecov warning can be safely ignored?

Yes. The coverage for snaps-simulator is generally lacking, because we haven't prioritised it in a while.