oxc vscode extension can't display import/no-cycle error if importing them by paths

[ChangeHow]

codesandbox demo: https://codesandbox.io/p/sandbox/pgk62j?file=%2Fsrc%2Fno-cycle%2Findex.ts

Kapture.2025-07-22.at.15.26.45.mp4

This issue will show right in CLI btw

[Sysix]

Your tsconfig.json must be at the root of your editor workspace and for CLI in your cwd.
Will create an option to override it like --tsconfig= ...

@camc314 not sure if we need to respect nested tsconfig.json files for oxlint and the language server.

/cc @camchenry for the future type aware linting

[camc314]

oxlint not the lang server supports nested tsconfigs at present. It's something i brought up in relation to type aware linting.
WIll make an issue to track support

[ChangeHow]

In my case, I shared a single one oxlintrc.json for every monorepos, it not a best practice i think.

But the keypoint is the extends in oxlintrc.json don't support @pkg/pkg-name to solve the shared config. Cause I shared a oxlint-base.json in libs/configs in my project and shared by workspace:* as internal deps in every monorepos.

[Sysix]

With the support of custom JS plugins, this should be supported too.

[ChangeHow]

With the support of custom JS plugins, this should be supported too.

Is it means I can remove the path like ../node_modules and instead of importing'@scope/name/oxlint-base.json'(or without explicit .json ext? )

I do remember that I've tried it in the earlier 0.x version, but oxlint can't resolve them.