Named import for 'any'-typed module doesn't work

Bug Report

🔎 Search Terms

any module export assignment named import

🕗 Version & Regression Information

TypeScript v4.1.2

💻 Code

mock.d.ts

declare const _: any;
export = _;

example.ts

import { a } from "./mock";

import * as b from "./mock";
const { c } = b;

const { d } = await import("./mock");

console.log(a, c, d);

tsconfig.json

{
  "compilerOptions": {
    "module": "ESNext",
    "strict": true,
    "target": "ESNext",
  },
  "include": [
    "./**/*.ts"
  ]
}

🙁 Actual behavior

The first import returns the diagnostic:

error TS2305: Module '"./mock"' has no exported member 'a'.

While c and d do not error.

🙂 Expected behavior

With an export being effectively any, I would expect default, namespace, dynamic and named imports to all behave as if the module was any. I cannot find any other way to declare a module in a fashion where the compiler treats any import from that module as any and does not issue diagnostics.

As implied in the above, there are certain situations where there is a need to "mock" a module where its shape cannot be statically determined at compile time.

Reproduziere den Bericht mit mock.d.ts, example.ts und tsconfig.json und verfolge anschließend, wie der TypeScript-Compiler benannte Importe aus einem als any typisierten Export-Assignment-Modul behandelt. Als erledigt gilt die Aufgabe, wenn der benannte Import nicht mehr TS2305 meldet und gleichzeitig das für Namespace- und dynamische Importe gezeigte Verhalten beibehalten wird.