3 ms·
> There will be no changes to the module system. None. It's finished. It's been finished for over a year. Any proposed changes must come with a clear reprodu
by avolcano 13y ago
> There will be no changes to the module system. None. It's finished. It's been finished for over a year. Any proposed changes must come with a clear reproducible bug that cannot be worked around or addressed with documentation.
This seems short-sighted, with ES6 modules now being used in production (through transpilers) and slowly making its way into SpiderMonkey and, more importantly, V8.
- jlongster 13y agoIt is a shame, but I just don't know how node would migrate to ES6 modules. I'm sure someone smarter than me could think up of a plan, but it seems like a huge amount of work. One of the strongest points about node is the amount of small reusable libraries available. They aren't about to ditch that.
- avolcano 13y agoSome thought has definitely been put into this problem: https://gist.github.com/domenic/4748675 https://gist.github.com/domenic/4748675 https://gist.github.com/wycats/51c96e3adcdb3a68cbc3#importing-a-node-module-by-processing-requires https://gist.github.com/wycats/51c96e3adcdb3a68cbc3#importin... (both of those are slightly out of date, syntax-wise, but are still conceptually current, IIRC)
- arxpoetica 13y agoGlad to hear it.