chore: upgrade typescript to ~5.5.0

[galargh]

• Because this PR includes a bug fix, relevant tests have been included.
• Because this PR includes a new feature, the change was previously discussed on an Issue or with someone from the team.
• I didn't do anything of this.

---

We use ${configDir} template variable in our tsconfig.json on v-next (e.g.

hardhat/config-v-next/tsconfig.json

Line 4 in bae09d3

"outDir": "${configDir}/dist",

) which has only been released in TypeScript 5.5 (https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-beta/#the-configdir-template-variable-for-configuration-files).

I've noticed it only, because I had my VSCode configured to use the workspace version of TypeScript, and when browsing files in v-next, it'd fail to resolve types.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
hardhat	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 8, 2024 1:46pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: bae09d3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[alcuadrado]

I've noticed it only, because I had my VSCode configured to use the workspace version of TypeScript,

I didn't understand the motivation for this PR at first, but I think this setting is the key reason, isn't it? Because I never had a problem, but I don't have that setting enabled (I probably should).

How would this work if it didn't have any version in the root of the project? I'm wondering because we only use that one in the v2 parts of the repo (i.e. packages/), not in the v3 ones.

Having said that, as this didn't create any compilation error in packages/, I don't see any reason not to merge it.

[galargh]

I've noticed it only, because I had my VSCode configured to use the workspace version of TypeScript,

I didn't understand the motivation for this PR at first, but I think this setting is the key reason, isn't it? Because I never had a problem, but I don't have that setting enabled (I probably should).

How would this work if it didn't have any version in the root of the project? I'm wondering because we only use that one in the v2 parts of the repo (i.e. packages/), not in the v3 ones.

Having said that, as this didn't create any compilation error in packages/, I don't see any reason not to merge it.

Yes, exactly.

By default, VSCode looks for TypeScript in the root node_modules. If we don't define typescript dependency at the root level, then the only option it has is to use the VSCode version of TypeScript. Unless one opens individual packages, of course.