News for hackers. Stuff that matters.

A comment on Node Modules at War: Why CommonJS and ES Modules Can’t Get Along. Parent comment

Re:Node Modules at War: Why CommonJS and ES Modules Can’t Ge... by dimgl on Thursday August 06, 2020 @02:34AM (#24068626)
> Node does not always fully initialize the dependency module before returning from require().

Unsure what this means. The only reason this happens is because an unfinished copy is provided to the dependency that is causing a circular reference.

[ Parent | on HN ]
Re:Node Modules at War: Why CommonJS and ES Modules Can’t Ge... by Doxin on Thursday August 06, 2020 @02:49AM (#24068698)
It means you can get a half-initialized module back from a require() call.
[ Parent | on HN ]
Re:Node Modules at War: Why CommonJS and ES Modules Can’t Ge... by kreetx on Thursday August 06, 2020 @05:56AM (#24069546)
Does that mean the required modules are not run?
[ Parent | on HN ]
Re:Node Modules at War: Why CommonJS and ES Modules Can’t Ge... by foreigner on Thursday August 06, 2020 @06:39AM (#24069721)
They are run, but if there are circular dependencies they are run _after_ require() returns.
[ Parent | on HN ]