What version of Oxlint are you using?

latest

What command did you run?

N/A

What does your .oxlintrc.json config file look like?

N/A

What happened?

Using this template because the bug report template said "If you are reporting a bug for Oxlint or the Oxc VS Code extension" but it doesn't seem the best fit. Changing the title to start with vscode: like I have seen on other issues though just in case. I am on version 1.32.0 of the vs code extension.

Given a scenario like mine where I have a backend and a frontend folder at the root (the frontend folder being basically a root for a typical frontend where my oxc configs and node modules live), there are enough settings to set and point the oxc plugin features to the right paths (although it seems a "oxc root dir" path setting would knock all of these out in my specific case). However there is a setting to turn on type aware linting, but not a setting for the path to the oxlint-tsgolint package, so my editor keeps reporting:

WARN  oxc_language_server::linter::isolated_lint_handler] Failed to initialize type-aware linting: Failed to find tsgolint executable. You may need to add the `oxlint-tsgolint` package to your project?

Here is a snippet from my settings for the workspace with an example of what I need

    "oxc.path.oxfmt": "frontend/node_modules/.bin/oxfmt",
    "oxc.path.oxlint": "frontend/node_modules/.bin/oxlint",
    "oxc.tsConfigPath": "frontend/tsconfig.json",
    "oxc.configPath": "frontend/.oxlintrc.json",
    "oxc.typeAware": true,
    "oxc.oxlint-tsgolintPath": "frontend/node_modules/.bin/tsgolint" //  <-------- Need this setting -------------

Could this setting be added? I would be happy to tackle this in a PR if it is not already in the works.

Thanks!