Support TypeScript 5.6.x-5.8.x

[mcmire]

This commit loosens the peer restriction on typescript to allow projects to upgrade to more recent versions of TypeScript (such as 5.8, the latest version at the time of writing). Similarly, the peer restriction on typescript-eslint has been loosened to support more recent versions.

Both of these packages have been updated in development as well.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​typescript-eslint/​visitor-keys@​8.24.1 ⏵ 8.28.0	+1
	@​typescript-eslint/​parser@​8.24.1 ⏵ 8.28.0	+1
	typescript-eslint@​8.24.1 ⏵ 8.28.0
	@​typescript-eslint/​type-utils@​8.24.1 ⏵ 8.28.0	+1		+1
	@​typescript-eslint/​types@​8.24.1 ⏵ 8.28.0	+1
	@​typescript-eslint/​utils@​8.24.1 ⏵ 8.28.0	+1		+1
	@​typescript-eslint/​scope-manager@​8.24.1 ⏵ 8.28.0	+1		+1
	@​typescript-eslint/​typescript-estree@​8.24.1 ⏵ 8.28.0	+1		+1
	@​typescript-eslint/​eslint-plugin@​8.24.1 ⏵ 8.28.0	+1		+1
	vite@​5.4.7 ⏵ 5.4.14	+1	+1	+1
	debug@​4.3.7 ⏵ 4.4.0	+1		+1
	typescript@​5.5.4 ⏵ 5.8.2			+1

View full report

[mcmire]

I figured that we could give consumers more flexibility for this package given that sometimes new versions bump the peer dependency on typescript and some don't.

[mcmire]

Really trying not to inconvenience existing projects this time around...

[Mrtenz]

Can you update the README of @metamask/eslint-config-typescript as well to use the new version?

[mcmire]

@Mrtenz Good call, done in 1e23503.

[mcmire]

Should we upgrade TypeScript all around in this PR? I'm just updating the dev depependency in the eslint-config-typescript package to prove that we don't get any peer dependency warnings when doing so, but it just occurred to me I could also do it in the root package as well. You could argue it would be out of scope, though, so I wasn't sure.

[Mrtenz]

Should we upgrade TypeScript all around in this PR? I'm just updating the dev depependency in the eslint-config-typescript package to prove that we don't get any peer dependency warnings when doing so, but it just occurred to me I could also do it in the root package as well. You could argue it would be out of scope, though, so I wasn't sure.

@mcmire Sounds good to me!

[mcmire]

Feedback addressed. Ready for another review.