[import/no-duplicates] False positive on imports in different typescript ambient modules

[chbdetta]

In an ambient file global.d.ts

declare module 'A' {
  import { ReactNode } from 'react';
}

declare module 'B' {
  import { ReactNode } from 'react';
}

import/no-duplicates complains about importing 'react' twice.

[ljharb]

Duplicate of #2054.

[chbdetta]

Is this a duplicate of #2054?
That issue is about importing the same library at the root level module. But here the importing happens in two different typescript ambient modules although they are declared in the same file.

[ljharb]

I think it's the same issue in that the problem is the typescript resolver pointing multiple modules to the same d.ts file, masking the actual value-space location that should be checked.

[chbdetta]

However, the plugin here seems to treat the import in two different typescript modules (A and B) as in one module.

I am expecting the plugin to treat the scope for module A and module B as they are defined in different files.

[ljharb]

Right - that's the issue in #2054. Both modules resolved to the same file, so the plugin considers them the same module.