Re:NPM and NodeJS should do more to make ES Modules easy to use
by maple3142 on Thursday June 20, 2024 @08:09PM
(#40744868)
I don't think it is a big problem given functions like fs.readFileSync already exists. It doesn't have to be a JS standard but be a server-side JS runtime specific function, which can be used when hacks are needed.
Re:NPM and NodeJS should do more to make ES Modules easy to use
by recursive on Thursday June 20, 2024 @08:29PM
(#40744963)
Node could just do that. `fs` isn't an ES spec, and nor does `importSync` need to be. The blame can't be placed on ESM for this.
Re:NPM and NodeJS should do more to make ES Modules easy to use
by tqwhite on Wednesday June 26, 2024 @11:01AM
(#40800849)
I agree. The blame belongs to the NodeJS steering committee. It's their failure and it's a big one.
The only excuse is that ESM happened during the big Deno Node wars when the community was split, everyone was mad and, apparently making dumb decisions.
I read that a new version of NodeJS has revised require() to bring in ESM modules. That's good enough. (I would prefer importSync() for clarity.)
IMO it would be a pandora's box of unending problems. A function doing a synchronous dynamic import creates a bad user experience. It's also a pretty rare circumstance in my experience. Dynamic imports are relatively uncommon to begin with. Having one that must be inside a non-async function is unheard of for me.
If you had your way, I think the net result would have been worse.