The module namespace object returned by __importStar is not the same when import the same module multiple times

🔎 Search Terms

• __importStar
• module object
• namespace object

🕗 Version & Regression Information

• Version: 6.0.2
• This is the behavior in every version I tried, and I reviewed the FAQ for entries about "namespace import". I did not found any information related to this.

⏯ Playground Link

https://www.typescriptlang.org/play/?target=99&jsx=0&module=1&ts=6.0.2#code/DYUwLgBADgjBC8ECWBbKB7ATmAFAIgDMBnPASgG4BYAKFEigCYFk0tdCSKaaAFTdFEiIgAdAENgwHAG1YAGmgMAuqRFgAFiAB2OGcRgLiy0ggB8EAN40INiAGN0WoulAjg6AOY59CeIiMUEAD0QRBgmACuIDQAvlzUQA

💻 Code

let p1 = import("fs");
let p2 = import("fs");

Promise.all([p1, p2]).then(([fs1, fs2]) => {
    console.log(fs1 === fs2); // expected true
});

🙁 Actual behavior

When the compiled code with node is run, false is printed. This means that the two imported module namespace object is different. each __importStar call create a new module namespace object.

🙂 Expected behavior

true should be printed. The module namespace objects of these two import("fs") should be the same object.
If we run this script directly by node without compiled, true will be printed.

Additional information about the issue

To reproduce this issue, "module" in "tsconfig.json" need to be set to "commonjs". This makes tsc use __importStar and require to import the module.

Comienza con el helper __importStar y la ruta del módulo CommonJS descrita en el issue, usando el ejemplo vinculado de Playground y una ejecución de Node.js como reproducción. Compara los dos resultados de Promise y sigue cómo las llamadas repetidas a import("fs") crean objetos de espacio de nombres; se considera terminado cuando el caso CommonJS compilado coincide con el comportamiento directo de Node.js y devuelve el mismo objeto.