🐛 BUG: [esinstall] outdated/wrong documentation?

[mindplay-dk]

Quick checklist

• I am using the latest version of Snowpack and all plugins. N/A

What package manager are you using?

npm

What operating system are you using?

Ubuntu 20 under WSL2

Describe the bug

I followed the directions for esinstall and it doesn't do what it says in the README.

import { install, printStats } from "esinstall";

(async () => {
  const result = await install(["preact", "htm"]);

  if (result.success) {
    printStats(result.stats);
  } else {
    console.error(JSON.stringify(result));
  }
})();

Output:

{"importMap":{"imports":{"htm":"./htm.js","preact":"./preact.js"}},"stats":{"direct":{"htm.js":{"size":1234,"gzip":662,"brotli":596},"preact.js":{"size":10043,"gzip":3992,"brotli":3674}},"common":{}}}

There is no success property in there?

(I don't know why we need to configure this with a build-script in the first place? Documentation is never a good substitute for something that actually emits an error message if you're using it wrong... Please consider adding a CLI front-end like we had in the old days with Pika? Installing an npm package as an ES module should be easy - no other project makes that easy since we lost Pika, and then again since the role of Snowpack completely changed from being essentially this... You had the simplest, most elegant solution to this... Please, consider making this simple again. 🙏)

Steps to reproduce

(see above)

Link to minimal reproducible example (optional)

No response

[mindplay-dk]

Even this doesn't work:

import { install, printStats } from "esinstall";

(async () => {
  const result = await install(["preact", "htm"]);

  printStats(result.stats);
})();

printStats just doesn't do anything - although from the console output above, you can see the stats property is there.

19k weekly downloads tells me somebody is successfully using this tool, or at least trying to?

Is this package maintained and supported or is it defunct?

[mindplay-dk]

Oh, okay, printStats doesn't actually print, heh... console.log(result.stats) and it works.

I'm going to guess the missing success flag has been replaced by a rejected Promise or something?

Looks like this is just a documentation issue.

(It would be really nice with a CLI front-end though - this really shouldn't be this hard.)