build(deps-dev): bump typescript from 4.3.5 to 4.4.2

[dependabot]

Bumps typescript from 4.3.5 to 4.4.2.

Release notes

Sourced from typescript's releases.

TypeScript 4.4.2

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 4.4.0 (Beta).
• fixed issues query for Typescript 4.4.1 (RC).
• fixed issues query for Typescript 4.4.2.

Downloads are available on:

• npm
• Visual Studio 2017/2019 (Select new version in project options)
• NuGet package

TypeScript 4.4 RC

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 4.4.0 (Beta).
• fixed issues query for Typescript 4.4.1 (RC).

Downloads are available on:

• npm
• Visual Studio 2017/2019 (Select new version in project options)
• NuGet package

TypeScript 4.4 Beta

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 4.3.0 (Beta).

Downloads are available on:

• npm
• Visual Studio 2017/2019 (Select new version in project options)
• NuGet package

Commits

• a10409c Bump version to 4.4.2 and LKG
• 5719423 Only provide hints for simple literals when 'literals' is specified. (#45557)
• d2a46a0 Cherry-pick PR #45554 into release-4.4 (#45555)
• a417917 Some cleanup around inlay hints types to get more-precise checking. (#45391)
• 7b0e665 Cherry-pick PR #45426 into release-4.4 (#45445)
• 55dd850 Update LKG.
• e9b1ff5 Fix __spreadArray for non-concat-spreadables (#45386)
• 11339d9 Update LKG
• c82ccf1 Cherry-pick PR #45399 into release-4.4 (#45404)
• 0648de8 Cherry-pick PR #45352 into release-4.4 (#45384)
• Additional commits viewable 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 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)

[yyx990803]

Looks like TS 4.4 breaks the build in two ways:

1. Caught errors are now unknown - this can be ignored by setting "useUnknownInCatchVariables": false in tsconfig.json

2. The type inference for h + return type of defineComponent seems to be broken. Spent some time looking into it but don't have a clear clue yet. /cc @pikax

[yyx990803]

Ok the h type inference issue is that now if the defineComponent call doesn't explicitly declare emits option, then h won't accept arbitrary onXXX handlers. Should be related to the emits to handler props inference PR (#3926) - /cc @Amour1688

[github-actions]

Size report

Path	Size
vue.global.prod.js	45.81 KB (0%)
runtime-dom.global.prod.js	30.22 KB (0%)
size-check.global.prod.js	17.42 KB (0%)

[pikax]

@yyx990803 fixed the issues with h the reason why it wasn't accepting an arbitrary onXXX was because the onXXX was having a type of undefined instead of function

I used catch(e :any) because the option useUnknownInCatchVariables was failing the api-extractor on test-dts.

What's missing now is fixing the tests which relied on namespaceURI which was removed

[yyx990803]

namesapceURI test cases can simply be fixed via (node as Element).namespaceURI for now