2 ms·
I agree, if we had all started with it, it is nice. But it completely breaks backwards compatibility with the whole existing node.js ecosystem, costing countles
by MCArth 4y ago
I agree, if we had all started with it, it is nice. But it completely breaks backwards compatibility with the whole existing node.js ecosystem, costing countless developer hours. It seems very likely to me a solution could have been found that would allow node to support the combination of esm and cjs.
- an1sotropy 4y agook, that makes sense (and sorry for making you answer twice). But I think sometimes a clean break is a necessary part of progress.