Update #1007 with exact node version that broke ESM

[cspotcode]

I mention that node 16.10.0 will break the ESM API, but it could be 16.9.x instead. When this happens, update the post accordingly.

nodejs/node#37468

[connorjclark]

Is this related to the error ReferenceError: exports is not defined in ES module scope received when trying to import a node builtin (like fs) when using ts-node/esm? (only get this when using moduleResolution: "node")

[cspotcode]

The breaking changes to ESM did not release in node v16.10.0.

[cspotcode]

No that's a user error, unrelated.

…

On Mon, Oct 18, 2021, 12:44 PM Dmitry Paliy ***@***.***> wrote: I could just confirm ReferenceError: exports is not defined in ES module scope when import fs/promises using both node 16.9.0 and 16.11.1 Is that issue related to this thread? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1453 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC35OBFWPIJMS3TD422SVDUHRFINANCNFSM5D4J3QRA> .