Bump typescript from 5.5.4 to 5.6.2

[dependabot]

Bumps typescript from 5.5.4 to 5.6.2.

Release notes

Sourced from typescript's releases.

TypeScript 5.6

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.6.0 (Beta).
• fixed issues query for Typescript 5.6.1 (RC).
• fixed issues query for Typescript 5.6.2 (Stable).

Downloads are available on:

• npm
• NuGet package

TypeScript 5.6 RC

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for TypeScript v5.6.1 (RC).
• fixed issues query for TypeScript v5.6.0 (Beta).

Downloads are available on:

• npm

TypeScript 5.6 Beta

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.6.0 (Beta).

Downloads are available on:

• npm
• NuGet package

Commits

• a7e3374 Bump version to 5.6.2 and LKG
• 2063357 🤖 Pick PR #59708 (LEGO: Pull request from lego/hb_537...) into release-5.6 (#...
• 4fe7e41 🤖 Pick PR #59670 (fix(59649): ts Move to a new file d...) into release-5.6 (#...
• 1a03e53 🤖 Pick PR #59761 (this can be nullish) into release-5.6 (#59762)
• 6212132 Update LKG
• bbb5faf 🤖 Pick PR #59542 (Fixing delay caused in vscode due t...) into release-5.6 (#...
• e6914a5 Bump version to 5.6.1-rc and LKG
• 34121c4 Update LKG
• 2a30c2a Merge remote-tracking branch 'origin/main' into release-5.6
• 936a79b Expose TypeChecker. getAwaitedType to public (#59268)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[github-actions]

Coverage report

Caution

Test run failed

St.❔	Category	Percentage	Covered / Total
🟢	Statements	100% (+55.05% 🔼)	0/0
🟢	Branches	100% (+75.28% 🔼)	0/0
🟢	Functions	100% (+72.66% 🔼)	0/0
🟢	Lines	100% (+54.85% 🔼)	0/0

Test suite run failed

Failed tests: 0/0. Failed suites: 2/2.

  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /home/runner/_work/hedera-wallet-connect/hedera-wallet-connect/node_modules/@walletconnect/modal/dist/index.js:2
    import { ModalCtrl, ThemeCtrl, ConfigCtrl, OptionsCtrl } from '@walletconnect/modal-core';
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      22 | import { EngineTypes, SessionTypes, SignClientTypes } from '@walletconnect/types'
      23 | import QRCodeModal from '@walletconnect/qrcode-modal'
    > 24 | import { WalletConnectModal } from '@walletconnect/modal'
         | ^
      25 |
      26 | import SignClient from '@walletconnect/sign-client'
      27 | import { getSdkError } from '@walletconnect/utils'

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/lib/dapp/index.ts:24:1)
      at Object.<anonymous> (src/lib/index.ts:23:1)
      at Object.<anonymous> (src/index.ts:21:1)
      at Object.<anonymous> (test/utils.test.ts:28:1)

---

  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /home/runner/_work/hedera-wallet-connect/hedera-wallet-connect/node_modules/@walletconnect/modal/dist/index.js:2
    import { ModalCtrl, ThemeCtrl, ConfigCtrl, OptionsCtrl } from '@walletconnect/modal-core';
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      22 | import { EngineTypes, SessionTypes, SignClientTypes } from '@walletconnect/types'
      23 | import QRCodeModal from '@walletconnect/qrcode-modal'
    > 24 | import { WalletConnectModal } from '@walletconnect/modal'
         | ^
      25 |
      26 | import SignClient from '@walletconnect/sign-client'
      27 | import { getSdkError } from '@walletconnect/utils'

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (src/lib/dapp/index.ts:24:1)
      at Object.<anonymous> (src/lib/index.ts:23:1)
      at Object.<anonymous> (src/index.ts:21:1)
      at Object.<anonymous> (test/dapp/DAppSigner.test.ts:36:1)

Report generated by 🧪jest coverage report action from 83a0327

[dependabot]

A newer version of typescript exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[rbarkerSL]

@dependabot rebase

[dependabot]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[rbarkerSL]

@dependabot recreate

[dependabot]

Superseded by #301.