Marcus Hultman

@c4spar What do you think about this? I think the feature itself is pretty solid - it really unlocks the full potential of completion. But it should probably not break...

> Would you guys be open to hosting binaries I second this! It would be nice to at least have a mirror repo with up to date binaries.

@polyomino-24 Now that Node 16 is LTS, it would be great if we could (1) get the node 16 image in to the registry, and (2) move the LTS tag...

@jordanebelanger The Node community maintains [official Node.js docker images](https://hub.docker.com/_/node?tab=description), which is likely why Google is not maintaining the same images anymore.

@bartlomieju

I'm surprised `Deno.test(...)` even makes it into bundled builds. Would this issue even be a problem if `Deno.test()` statements were stripped out of `deno bundle`-bundles (optionally with cli flag)? Would...

Implementing this as a [Configuration file](https://deno.com/[email protected]/getting_started/configuration_file) option (`"npmRegistry"`) in https://github.com/denoland/deno/pull/19317

@esnho The env was changed to `NPM_CONFIG_REGISTRY`.

Getting this again now using `import { FaBeer } from 'https://esm.sh/[email protected]/fa';` esm.sh version: v94 Deno version: 1.25.0

@ije When running `deno run https://esm.sh/[email protected]/fa` ``` error: Uncaught SyntaxError: The requested module '/v95/[email protected]/deno/lib/esm/iconContext.js' does not provide an export named 'DefaultContext' at (https://esm.sh/v95/[email protected]/deno/lib/esm/iconBase.js:2:210) ```