Update dependency typescript to ~5.3.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
typescript (source)	~5.2.2 -> ~5.3.0

---

Release Notes

Microsoft/TypeScript (typescript)

v5.3.2: TypeScript 5.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.3.0 (Beta).
• fixed issues query for Typescript 5.3.1 (RC).
• fixed issues query for Typescript 5.3.2 (Stable).

Downloads are available on:

• NuGet package

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
console	❌ Failed (Inspect)		Nov 20, 2023 8:09pm

[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

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"~5.3.0" from the root project
npm ERR!   peer typescript@">=4.2.0" from [email protected]
npm ERR!   node_modules/ts-api-utils
npm ERR!     ts-api-utils@"^1.0.1" from @typescript-eslint/[email protected]
npm ERR!     node_modules/@typescript-eslint/eslint-plugin
npm ERR!       dev @typescript-eslint/eslint-plugin@"~6.9.0" from the root project
npm ERR!     ts-api-utils@"^1.0.1" from @typescript-eslint/[email protected]
npm ERR!     node_modules/@typescript-eslint/type-utils
npm ERR!       @typescript-eslint/type-utils@"6.9.0" from @typescript-eslint/[email protected]
npm ERR!       node_modules/@typescript-eslint/eslint-plugin
npm ERR!         dev @typescript-eslint/eslint-plugin@"~6.9.0" from the root project
npm ERR!     1 more (@typescript-eslint/typescript-estree)
npm ERR!   1 more (tsconfck)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional typescript@">= 4.7.x <= 5.2.x" from [email protected]
npm ERR! node_modules/msw
npm ERR!   dev msw@"^2.0.7" from the root project
npm ERR!   peer msw@">=1.0.0" from @mswjs/[email protected]
npm ERR!   node_modules/@mswjs/http-middleware
npm ERR!     dev @mswjs/http-middleware@"^0.8.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/typescript
npm ERR!   peerOptional typescript@">= 4.7.x <= 5.2.x" from [email protected]
npm ERR!   node_modules/msw
npm ERR!     dev msw@"^2.0.7" from the root project
npm ERR!     peer msw@">=1.0.0" from @mswjs/[email protected]
npm ERR!     node_modules/@mswjs/http-middleware
npm ERR!       dev @mswjs/http-middleware@"^0.8.0" 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/625a2f/250687/cache/others/npm/_logs/2023-11-20T20_07_37_533Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/625a2f/250687/cache/others/npm/_logs/2023-11-20T20_07_37_533Z-debug-0.log

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (~5.3.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.