linter: import/no-cycle with TypeScript + ESM

[Boshen]

Discussed in https://github.com/oxc-project/oxc/discussions/6906

^{Originally posted by LukeNotable October 26, 2024} Trying out oxlint for the first time in the hope that it can at least give us a fast check on import/no-cycle. I have a TypeScript project using ESM, thus files like:

// foo.ts
import { Bar } from './bar.js';

// bar.ts
import { Foo } from './foo.js';

However, the rule fails to flag this as a problem. But if I remove the .js extension, the rule behaves correctly. However, the .js extension is required under ESM.

I recall a similar issue with the original eslint-plugin-import, which required eslint-import-resolver-typescript, and I see there's an oxc-resolver, so I wonder if I just need to do some additional configuration to use it.

[Boshen]

context: https://www.typescriptlang.org/docs/handbook/modules/reference.html#common-features-and-processes

[DonIsaac]

Sounds like we need to modify the resolver?

[Smrtnyk]

@Boshen is this fix already available in v 0.15 of linter?