I want to put it out here, why I think oxlint "base" config search should also search upwards the cwd, like oxfmt does and oxlint --lsp ❗

Users in a monorepo setup will execute the command in their current package/app. Something like /project/packages/package oxlint. With good luck there is already a .oxlintrc.json or another config file, which it will detect.
If not it should imo still find the .oxlintrc.json from /project/ directory.

This was specially problem in LSP with nested multi root workspaces.
The issue & fix: #19061 & #19062

I would argue that CLI will hit the same problem when integrated with other tools like turborepo, where the cwd is not directly controlled by the user?

Originally posted by @Sysix in voidzero-dev/vite-plus#1378 (comment)