`console.log` is a little verbose when using `deno` about runtime-js

[whitequark]

Amazingly, the yowasp npm package works great with Deno

The package is intentionally written in a way that uses as few host APIs as possible, and whenever it does, uses them in the simplest manner possible. Plus there's explicit portability between browser and Node. (I'm not sure which branch Deno takes--I would suspect Node, but they only differ in whether resources are grabbed with fetch or fs.readFile, so it doesn't matter a whole lot.)

However, it does cause a lot of console.log usage under the CLI:

Yeah. This is sort of intentional, I am currently loading the resources serially and not in parallel, so I wanted some progress indication. I will probably just remove that after I request all the promises in parallel. Happy to merge a PR doing that, as well.