fix(oxc): tolerate stdout notices ahead of oxlint's JSON payload

[dvcolomban]

Summary

parseOxlintOutput calls JSON.parse directly on oxlint's raw stdout. When oxlint's own file-discovery matches zero files (e.g. a package in a monorepo that isn't opted into oxlint, or any project with an empty/mismatched include glob), oxlint prints a human-readable notice — No files found to lint. Please check your paths and ignore patterns. — to stdout before the JSON payload, even when invoked with -f json. That leading line breaks JSON.parse, and the devtools-oxc:run-lint RPC surfaces a generic Oxlint returned invalid JSON error instead of reporting a clean zero-diagnostics result.

Reproduced directly:

$ oxlint -f json
No files found to lint. Please check your paths and ignore patterns.
{ "diagnostics": [],
              "number_of_files": 0,
              ...
            }

Fix

parseOxlintOutput now skips to the first { in stdout before parsing, so any leading notice oxlint prints doesn't break JSON parsing. Falls back to parsing the raw string unchanged if no { is found, preserving existing error behavior for genuinely invalid output.

Test plan

• Added a regression test reproducing the exact stdout shape (notice line + JSON) and asserting it now parses to a zero-diagnostics summary.
• pnpm vitest run packages/oxc/src/node/__tests__/lint-results.test.ts — 6/6 passing.
• pnpm -C packages/oxc run lint — clean.

[pkg-pr-new]

Open in StackBlitz

@vitejs/devtools

npm i https://pkg.pr.new/@vitejs/devtools@476

@vitejs/devtools-kit

npm i https://pkg.pr.new/@vitejs/devtools-kit@476

@vitejs/devtools-oxc

npm i https://pkg.pr.new/@vitejs/devtools-oxc@476

@vitejs/devtools-rolldown

npm i https://pkg.pr.new/@vitejs/devtools-rolldown@476

@vitejs/devtools-vite

npm i https://pkg.pr.new/@vitejs/devtools-vite@476

@vitejs/devtools-vitest

npm i https://pkg.pr.new/@vitejs/devtools-vitest@476

commit: 22550b0