[Feature Request][Enhancement] json file output

[MIreland]

Right now, there isn't a clean way to get JSON output into a file. In this sample project, I use:

"oxlint:json": "mkdir -p artifacts && oxlint src --format json > artifacts/oxc-lint.json",

But the output is invalid:

[
	{"message": "eslint-plugin-react(jsx-no-target-blank): Using target=`_blank` without rel=`noreferrer` (which implies rel=`noopener`) is a security risk in older browsers: see https://mathiasbynens.github.io/rel-noopener/#recommendations","severity": "warning","causes": [],"help": "add rel=`noreferrer` to the element","filename": "src/App.tsx","labels": [{"span": {"offset": 595,"length": 8}}],"related": []},
	{"message": "eslint-plugin-react(jsx-no-target-blank): Using target=`_blank` without rel=`noreferrer` (which implies rel=`noopener`) is a security risk in older browsers: see https://mathiasbynens.github.io/rel-noopener/#recommendations","severity": "warning","causes": [],"help": "add rel=`noreferrer` to the element","filename": "src/App.tsx","labels": [{"span": {"offset": 727,"length": 8}}],"related": []}
]

Finished in 10ms on 5 files with 89 rules using 10 threads.
Found 2 warnings and 0 errors.

On a similar note (I can make this a separate ticket if desired), we would REALLY appreciate being able to specify multiple reporters- specifically, we want human-readable terminal output at the same time we generate machine-readable JSON output.

We currently use this eslint wrapper to achieve this with eslint. It would be great to offer it natively for oxlint.

[R11baka]

Not clear what is expected result? add an option to save to file ? or change formatting ?

[MIreland]

Two requests wrapped in one here:

• allow saving JSON to a file via a flag
• allow using multiple reporters (save to file + still have terminal output)

[Boshen]

allow using multiple reporters (save to file + still have terminal output)

If eslint doesn't support this, I wonder if you can run oxlint twice with different formatters given oxlint is super fast 😅

[MIreland]

@Boshen - that definitely would work, but feels a bit verbose to have every script look like:
"lint": "oxlint --import-plugin --jest-plugin --jsx-a11y-plugin --react-perf-plugin --config=../../oxlint.json && oxlint --import-plugin --jest-plugin --jsx-a11y-plugin --react-perf-plugin --config=../../oxlint.json --format=json"

If we don't want to allow multiple reporters, how would you feel about me opening a PR with a default-with-json format that requires a --output-filename parameter?

[Boshen]

@MIreland Happy to accept any eslint cli options, https://eslint.org/docs/latest/use/command-line-interface#-o---output-file

On accepting multiple formatters, you may raise another issue for it, although eslint doesn't accept multiple formatters, I may be able to bend the rule because it's not that hard to implement 🤔