kumavis

congrats on shipping

@ljharb :wave:

this seems to work, would be nice to support a prefix like iojs (maybe `local-`) ```bash # from node dir tools/install.py install /home/xyz/.nvm/versions/node/ v100.0.4 nvm use v100.0.4 ```

+1

This mozilla compat table has some useful data, including `Firefox for Android` https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs

this solved the issue, but probably better to solve inside the digitalocean provider implementation `dropletId: droplet.id.apply(id => parseInt(id, 10)),`

https://github.com/pulumi/pulumi-digitalocean/issues/600 https://github.com/pulumi/pulumi/issues/17841

looks like it is intentional https://github.com/ds300/patch-package/issues/86 workaround is `NODE_ENV=test`

@lukewagner looking to have a wasm module perform some async network I/O mediated by JS - any way of doing this with the current api?

Thanks @lukewagner found `emscripten_async_wget` [defined in js](https://github.com/kripken/emscripten/blob/07b87426f898d6e9c677db291d9088c839197291/src/library_browser.js#L755-L786) This calls `Runtime.dynCall` [here](https://github.com/kripken/emscripten/blob/07b87426f898d6e9c677db291d9088c839197291/src/library_browser.js#L763) ``` js Runtime.dynCall('vi', callback, [allocate(intArrayFromString(_file), 'i8', ALLOC_STACK)]); ``` `Runtime.dynCall` is defined [here](https://github.com/kripken/emscripten/blob/07b87426f898d6e9c677db291d9088c839197291/src/runtime.js#L194-L214) which calls the exported wasm function [here](https://github.com/kripken/emscripten/blob/07b87426f898d6e9c677db291d9088c839197291/src/runtime.js#L204)...