News for hackers. Stuff that matters.
Re:The state of JavaScript modules by _pmf_ on Monday May 29, 2017 @03:51AM (#14437953)
> The one thing that I really miss is that most (all?) JS module implementations really seem to be focused on static compile workflows.

That's what baffles me coming from Java and C#; I can have dynamically loaded modules with strongly typed interfaces in these ecosystems, but not in any JS module system.

Re:The state of JavaScript modules by bfred_it on Monday May 29, 2017 @04:24AM (#14438050)
require() is dynamic and import() will be too. What are you talking about?

JavaScript is not a typed language (yet?) so it's like expecting pigs to fly.

Re:The state of JavaScript modules by _pmf_ on Monday May 29, 2017 @04:53AM (#14438147)
With "dynamic", I mean "pulled in at runtime" vs. "pulled in at compile time". See http://2ality.com/2017/01/import-operator.html
Re:The state of JavaScript modules by Vinnl on Monday May 29, 2017 @06:33AM (#14438432)
Isn't that exactly what `import()` is?