I have been working on migrating Sentry's codebase to use oxlint but the migration path has a hard dependency on type awareness and typescript version.

The issue

Since we are staying on 5.x for the time being we would like to still use oxlint but disable the tsconfig verification, which is mostly fired for old deprecated options like alwaysStrict and other changes like baseDir and rootDir.

Turning the rule off via cli or oxlint config doesn't work because it seems like it's not a "real" rule. It's produced during program creation when TypeScript fails to parse or validate a tsconfig.json unlike the other rules.

Suggestion/Feature Request

I'm thinking large codebases can benefit from this by silencing this type of errors temporarily until they are able to migrate to TS 6.0/7.0 since the tsconfig doesn't really stop those rules from working.

I cobbled something together locally by adding an environment variable: TSGOLINT_REPORT_TSCONFIG_ERRORS=false, this works today without any changes on the oxlint side. It's technically "suppressing" it rather than "disabling it".

I considered adding top-level payload flag but that requires changes on oxlint side to pass it along, so env variable was the easiest option to test with and is "secret" enough to not encourage everyone adopting it.

What do you folks think? I'm happy to PR this if you think it's worth adding.