Allow oxlint / oxfmt being setup in workspace subfolders and having the oxc VS Code extension support that

[hansmbakker]

I have one repo containing a .NET Aspire setup with

• multiple .NET projects for services / backends
• multiple Node / React projects for a frontend and backend-for-frontend

like this:

/ (root)
/README.md
/src
/src/Project.AppHost                           (.NET Aspire AppHost project)
/src/Project.Backend                           (.NET ASP.NET Core backend)
/src/copilotkit-runtime                        (Node.js / TypeScript based backend-for-frontend)
/src/copilotkit-runtime/oxlintrc.json
/src/copilotkit-runtime/package.json
/src/copilotkit-runtime/...
/src/frontend                                  (Vite / React / TypeScript based SPA frontend)
/src/frontend/oxlintrc.json
/src/frontend/package.json
/src/frontend/...

Relevant parts of package.json:

{
  "name": "frontend",
  "version": "0.0.0",
  "private": true,
  "type": "module",
  "scripts": {
    "dev": "vite",
    "build": "tsc -b && vite build",
    "lint": "oxlint .",
    "lint:fix": "oxlint --fix",
    "preview": "vite preview",
    "format": "oxfmt",
    "format:check": "oxfmt --check",
  },
  "dependencies": {
    [...]
  },
  "devDependencies": {
    "oxfmt": "^0.54.0",
    "oxlint": "^1.69.0",
    "oxlint-tsgolint": "^0.23.0",
  }
}

I believe package.json and oxlintrc.json are not relevant to have in the root. That's why I want them only in the typescript-based folders. Running npm run lint works fine from the frontend folder.

However, the Oxc VS Code extension does not work well if it is not setup like that.

Pointing the VS Code extension to a custom location can only point to one subfolder.

This is a feature request to support a setup like this.