ecosystem

require(esm) Killed the Second Build, Not the Second Copy

Being able to require() an ES module removes the reason most packages shipped two builds. The dual package hazard is a layout problem, and it survived.