build(solidity): raise TypeScript to 6.0.3 in both packages

[mswilkison]

Stacked on #4207.

6.0.3 is the last TypeScript release with a JavaScript API. I checked what 7.x actually ships:

node_modules/typescript/lib/  →  getExePath.js  tsc.js  version.cjs
require("typescript").transpileModule       → undefined
require("typescript").createProgram         → undefined
require("typescript").createLanguageService → undefined

There is no lib/typescript.js — the 7.x package is a launcher for the Go binary. ts-node (which hardhat 2 uses to run hardhat.config.ts and the tests), @typescript-eslint, typechain and prettier's TS parser all drive that API, so installing 7 today would break the build, the linter and codegen at once. 6.x is where this stops until those ship tsgo support.

Three defaults changed, all pinned back

This is a version bump, not a tightening, so each new default is pinned to what the packages already do:

Default	Effect if left alone	Pinned to
strict now on	strict debt in both packages	"strict": false (random-beacon keeps its existing noImplicitAny)
@types/* no longer auto-included	mocha/chai globals vanish — 1 732 diagnostics in ecdsa alone	"types": [...] naming the packages that contribute globals
rootDir required for multi-directory projects	hardhat refuses to start	"rootDir": "."

The rootDir one is the reason to run more than the type checker: tsc --noEmit stays perfectly green while hardhat test dies with TS5011.

Turning strict on is real work and belongs in its own PR.

The ES5 export bundle is on borrowed time

Both packages publish an export/ bundle built through tsconfig.export.json at target: es5. In TypeScript 6, both that target (TS5107) and downlevelIteration (TS5101) are deprecated, and both are removed in TypeScript 7.

They are silenced here with "ignoreDeprecations": "6.0" rather than removed, because at target: es5 downlevelIteration genuinely changes emit for for…of over non-array iterables, and that bundle is consumed by downstream packages. In ecdsa this also matters for prepare, which runs the same build on install — so getting it wrong breaks yarn install, not just publishing.

Raising the export target off ES5 is a prerequisite for TypeScript 7 and is tracked separately.

Verification

Both packages, on 6.0.3:

	random-beacon	ecdsa
tsc --noEmit	0 errors	0 errors
tsc -p tsconfig.export.json	builds	builds
yarn lint	0 errors	0 errors
yarn test	955 passing / 0 failing	673 passing / 0 failing

Lockfile churn is 18 lines per package, all typescript.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 16ad78b8-5025-4e50-a81d-7382d677d866

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/solidity-typescript-6

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}