feat: add proper wrapping for esm and Deno by updating dependencies

[shadowspawn]

This is yet another approach for adding wrapping for ESM and Deno, see also #119 #139 #140 !

Problem

Only CJS currently gets smart wrapping (#89 #113 #138 yargs/yargs#2112)

Solution

Upgrade to newer ansi dependencies which are ESM and use rollup to transpile the CJS version.

• the tests are refactored so that full tests run for both CJS and ESM
• add ESM test to npm run-script for test, run both cjs and esm tests together

Notes for interest of reviewers:

• The ansi dependencies for Deno are specified implicitly by package.json. I like package.json so have a single source of truth for dependency versions, but I don't know the tradeoffs vs using an URL to a CDN, and if it works ok when published to deno.land.
• Two of the transient dependencies are cjs, so the esm build is no longer "pure" esm.
• Not updating to rollup@3 as it requires node 14. (And cliui still only requires node 12.)
• Not updating to string-width@6 as it requires requires node 16.

[bcoe]

Feeling inspired to do a little bit of open source again, apologies for radio silence.

Any preference between this implementation and @isaacs #139

[isaacs]

I'm happy to switch back from my fork once it has the same behavior on esm as cjs, whether it's the pr I sent or this one or some other one.

[shadowspawn]

I was concerned the approach with aliases in #139 and used in jackspeak triggered multiple problem reports from users of yarn. We are using rollup though various yargs repos to help with the hybrid cjs/esm, so already have a tool for the job.

Reports of problems with yarn 1:

• fix: handle strings the same in cjs, esm, and deno #139 (comment)
• Dependency on @isaacs/[email protected] is broken isaacs/jackspeak#5
• [Bug]: string-width dependency stops storybook from executing storybookjs/storybook#22431

And one problem with yarn 3:

• fix: handle strings the same in cjs, esm, and deno #139 (comment)

[shadowspawn]

There was a clash between versions of TypeScript from 4.7 and rollup@2 that was fixed in [email protected], but that rollup requires node 14. Pinning back TypeScript to 4.6.4 works around the problem.

• rollup-plugin-ts not compatible with TypeScript 4.7-4.9 wessberg/rollup-plugin-ts#196

(Now, what is going wrong with that coverage check...)

[isaacs]

There is absolutely no reason for any module to keep supporting node 14, let alone node 12. (For that matter, I obviously don't see the point in trying to support yarn 1, but here we are.)

If someone is using EOL versions of node, they are already off the supported landscape, and can be expected to either very carefully lock down everything, or be broken repeatedly.

[shadowspawn]

There is absolutely no reason for any module to keep supporting node 14, let alone node 12

Yes, I am just trying to work with the current constraints so this PR is independent of a bumping minimum node to (say) 18. (And freshly reminded of what a pain that can be.)

[bjester]

Just wanted to say that I appreciate the effort put into this, as it helps immensely in transitioning fully to ESM. The fork of this package used in glob has only caused us (learning equality) issues, specifically as time hasn't been put into upgrading yarn (yet).