build!: drops Node 6 and 4. begin following Node.js LTS schedule #89
@QmarkC thanks for the update. One thing on my mind, as we move towards the next major of each of yargs' dependencies, is if we can prefect the approach here then we should be able to ship a version of yargs that is fully functional in Node ESM, Node CJS, browser ESM, and Deno...
This is completely unrelated to dropping old Node.js versions, except that I'd like to hold off on us taking the next breaking change for these libraries until we've dialed in the approach I'm describing.