feat(linter): add typescript/strict-void-return rule

[camc314]

No description provided.

[camc314]

• feat(linter): add typescript/dot-notation rule #19442
• feat(linter): add typescript/strict-void-return rule #19441 👈 (View in Graphite)
• feat(linter): add typescript/consistent-type-exports rule #19440
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

Merging this PR will not alter performance

✅ 47 untouched benchmarks
⏩ 3 skipped benchmarks¹

---

_{Comparing c/02-14-feat_linter_add_typescript_strict-void-return_rule (bb4f5f1) with c/02-14-feat_linter_add_typescript_consistent-type-exports_rule (b57c409)²}

Footnotes

1. 3 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on c/02-14-feat_linter_add_typescript_consistent-type-exports_rule (b57c409) during the generation of this report, so 0227d66 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[camc314]

Merge activity

• Feb 16, 6:42 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Feb 16, 6:51 PM UTC: camc314 added this pull request to the Graphite merge queue.
• Feb 16, 7:08 PM UTC: Merged by the Graphite merge queue.

[Copilot]

Pull request overview

Adds a new type-aware TypeScript lint rule (typescript/strict-void-return) to the linter, exposing configuration and wiring it into the rule registry and CLI fixture coverage.

Changes:

• Introduces StrictVoidReturn rule module with allowReturnAny configuration serialization/deserialization.
• Registers the rule in the TypeScript rules module and generated rule dispatch/runner glue.
• Adds/updates oxlint fixtures and snapshots to cover default behavior and the allowReturnAny option.

Reviewed changes

Copilot reviewed 11 out of 13 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
crates/oxc_linter/src/rules/typescript/strict_void_return.rs	Adds the new rule definition + config (including allowReturnAny) and config (de)serialization.
crates/oxc_linter/src/rules.rs	Exposes the new TypeScript rule module.
crates/oxc_linter/src/generated/rules_enum.rs	Registers the rule in the generated rule enum, IDs, and dispatch methods.
crates/oxc_linter/src/generated/rule_runner_impls.rs	Adds generated RuleRunner impl for the new rule.
apps/oxlint/src/snapshots/fixtures__tsgolint_rule_options_--type-aware@oxlint.snap	Updates snapshot output to include the new rule firing in the options fixture run.
apps/oxlint/src/snapshots/fixtures__tsgolint_--type-aware@oxlint.snap	Updates snapshot output to include the new strict-void-return fixture result and updated counts.
apps/oxlint/fixtures/tsgolint_rule_options/test.ts	Adds fixture assertions for allowReturnAny behavior.
apps/oxlint/fixtures/tsgolint_rule_options/.oxlintrc.json	Enables/configures typescript/strict-void-return with allowReturnAny: true for the options fixture.
apps/oxlint/fixtures/tsgolint/strict-void-return.ts	Adds a dedicated fixture file that triggers the rule.
apps/oxlint/fixtures/tsgolint/.oxlintrc.json	Enables typescript/strict-void-return in the tsgolint fixture set.