chore(deps-dev): bump typescript from 5.3.2 to 5.3.3

[dependabot]

Bumps typescript from 5.3.2 to 5.3.3.

Release notes

Sourced from typescript's releases.

TypeScript 5.3.3

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).
• fixed issues query for Typescript 5.3.3 (Stable).

Downloads are available on:

• NuGet package

Commits

• 63717cf Bump version to 5.3.3 and LKG
• 4c2afa7 🤖 Pick PR #56627 (Transpile jsdoc parsing mode) into release-5.3 (#56629)
• ba3d2b0 🤖 Pick PR #56434 (Fix support for intersections in te...) into release-5.3 (#...
• f3808c4 🤖 Pick PR #56504 (Fixed an issue in boolean compariso...) into release-5.3 (#...
• b4fe221 Cherry-pick #56489 into release-5.3 (#56490)
• f750eb3 Pick #56485 into release-5.3 (#56486)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
typescript	5.3.2...5.3.3	None	+0/-0	32 MB	typescript-bot

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
Chronological version anomaly	typescript	5.3.3	Previous Chronological: [email protected] (12/6/2023, 7:09:35 AM) Previous Semver: [email protected] (11/20/2023, 5:35:59 PM)	@tachibana-shin/[email protected] via package.json package.json

Next steps

What is a chronological version anomaly?

Semantic versions published out of chronological order.

This could either indicate dependency confusion or a patched vulnerability.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore [email protected]

[pr-explainer-bot]

Pull Request Review Markdown

Hey there! 👋 Here's a summary of the previous tasks and their results. Let's dive in!

Changes

1. Updated typescript dependency from 5.3.2 to 5.3.3 in package.json (line 7)
2. Updated tsutils dependency from 3.21.0([email protected]) to 3.21.0([email protected]) in pnpm-lock.yaml (line 14)
3. Updated @typescript-eslint/utils dependency from 5.62.0([email protected])([email protected]) to 5.62.0([email protected])([email protected]) in pnpm-lock.yaml (line 23)
4. Updated @typescript-eslint/typescript-estree dependency from 5.62.0([email protected]) to 5.62.0([email protected]) in pnpm-lock.yaml (line 26)
5. Updated @typescript-eslint/parser dependency from 5.62.0([email protected])([email protected]) to 5.62.0([email protected])([email protected]) in pnpm-lock.yaml (line 32)
6. Updated @typescript-eslint/type-utils dependency from 5.62.0([email protected])([email protected]) to 5.62.0([email protected])([email protected]) in pnpm-lock.yaml (line 38)
7. Updated is-immutable-type dependency from 1.2.9([email protected])([email protected]) to 1.2.9([email protected])([email protected]) in pnpm-lock.yaml (line 45)
8. Updated tsutils dependency from 3.21.0([email protected]) to 3.21.0([email protected]) in pnpm-lock.yaml (line 52)
9. Updated typescript dependency from 5.3.2 to 5.3.3 in pnpm-lock.yaml (line 59)

Suggestions

1. In package.json, consider aligning the version numbers for better readability (line 7)
2. In pnpm-lock.yaml, consider aligning the version numbers for better readability (lines 14, 23, 26, 32, 38, 45, 52, 59)

Bugs

1. Potential bug in pnpm-lock.yaml at line 14: tsutils dependency version is not aligned with typescript version
2. Potential bug in pnpm-lock.yaml at line 23: @typescript-eslint/utils dependency version is not aligned with typescript version
3. Potential bug in pnpm-lock.yaml at line 26: @typescript-eslint/typescript-estree dependency version is not aligned with typescript version
4. Potential bug in pnpm-lock.yaml at line 32: @typescript-eslint/parser dependency version is not aligned with typescript version
5. Potential bug in pnpm-lock.yaml at line 38: @typescript-eslint/type-utils dependency version is not aligned with typescript version
6. Potential bug in pnpm-lock.yaml at line 45: is-immutable-type dependency version is not aligned with typescript version
7. Potential bug in pnpm-lock.yaml at line 52: tsutils dependency version is not aligned with typescript version
8. Potential bug in pnpm-lock.yaml at line 59: typescript dependency version is not aligned with typescript version

Improvements

1. In pnpm-lock.yaml, the repetitive pattern of updating dependencies can be refactored into a helper function for better readability. Here's an example:

{
  "task1": [
    "1. Updated `@tachibana-shin/eslint-config` version from `1.1.1([email protected])([email protected])` to `1.1.1([email protected])([email protected])`",
    "2. Updated `typescript` version from `5.3.2` to `5.3.3`"
  ],
  "task2": [
    "1. In line 15, consider using a specific version for `@tachibana-shin/eslint-config` instead of using the `^` specifier.",
    "2. In line 44, consider using a specific version for `@types/node` instead of using the `^` specifier.",
    "3. In line 664, consider using a specific version for `typescript` instead of using the `^` specifier.",
    "4. In line 716, consider using a specific version for `@typescript-eslint/eslint-plugin` instead of using the `^` specifier.",
    "5. In line 744, consider using a specific version for `@typescript-eslint/parser` instead of using the `^` specifier.",
    "6. In line 760, consider using a specific version for `@typescript-eslint/type-utils` instead of using the `^` specifier.",
    "7. In line 770, consider using a specific version for `@typescript-eslint/typescript-estree` instead of using the `^` specifier.",
    "8. In line 785, consider using a specific version for `@typescript-eslint/types` instead of using the `^` specifier."
  ]
}

Rating

Rate the code from 0 to 10 based on the following criteria:

• Readability
• Performance
• Security

Feel free to add a brief explanation for each criterion.

That's it! Let me know if you need any further assistance. Good luck with the pull request! 🚀