fix(linter/plugins): define RegExp.escape for tsc

[overlookmotel]

Fix a couple of errors that get flagged by TypeScript in VS Code, because it doesn't recognise RegExp.escape. Oxlint's typecheck doesn't flag it (presumably tsgo is aware of this new addition to the language), but it's still annoying having red squiggles in VS Code. This PR fixes that.

[overlookmotel]

• fix(linter/plugins): define RegExp.escape for tsc #20077 👈 (View in Graphite)
• docs(linter/plugins): move comment about "bivariance hack" into generated code #20082
• fix(linter/plugins): fix types for walkProgram and walkProgramWithCfg #20081
• refactor(linter/plugins): debug assert that values passed via NAPI are not undefined #20070
• refactor(linter/plugins): clarify types #20069
• test(linter/plugins): add types test for VisitorObject #20066
• refactor(linter/plugins): enable TS strict option #19675
• fix(linter/plugins): fix type definition for VisitorObject #20065
• 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 changes, fast-track this PR to the front of the merge queue

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.

[camc314]

I don't think we need this - tsgolint ships with es2025 types

[Copilot]

Copilot wasn't able to review any files in this pull request.

[overlookmotel]

I don't think we need this - tsgolint ships with es2025 types

Rationale is explained in PR description that I just added. Personally I think it's worthwhile, but if you disagree, feel free to close this - I don't care enough to argue!

[connorshea]

Alternatively, we could upgrade to the TS 6.0 release candidate? microsoft/TypeScript#63046

[overlookmotel]

The source of the red squiggles in VS Code isn't Oxlint, it's whatever version of TypeScript is used by VS Code itself. I don't think that's within our control, right?

People hacking on Oxc could disable TS in VS Code and rely purely on Oxlint type-check but (a) most people won't do that and (b) personally I like to keep it enabled as a failsafe - and to discover if Oxlint type-check is missing anything.

[camc314]

it's just the Regex.escape line in the editor right?

Users can update to the preview editor extension or use the native preview I think?

[overlookmotel]

It's just the Regex.escape line in the editor right?

Yes, that's all it is.

To be honest, I don't really understand why you're opposed. We have the same code in Oxfmt:

oxc/apps/oxfmt/test/cli/utils.ts

Lines 9 to 14 in e4aa5b5

	// NOTE: TS's ESNext is not yet reached to ES2025...
	declare global {
	interface RegExpConstructor {
	escape(str: string): string;
	}
	}

But whatever the reason, I see that you are firmly opposed, so closing.