Jason Miller

Ah yes, we're filtering out wasm by accident. Barring that, you can use the URL prefix to load WASM: ```js import url from 'url:./foo.wasm'; ```

Ah yeah that's possible. Is this after running npm install to ensure the file is there? We don't currently stream wasm to disk during auto-install.

I think this might work if you pass `--external lib/external.js` (not a wildcard).

The official Rollup commonjs plugin won't work with WMR's dev server, because it's not a full Rollup implementation. The version number is fake, but even if that were updated this...

@rschristian I thought it was because of the `scheduler` package?

Interesting - I had assumed Yarn Workspaces would be setting up symlinks for this, but I guess they're relying on Node resolution looking into parent directories' node_modules. A prerequisite to...

Interesting! This is actually a bug in [@babel/preset-modules](https://github.com/babel/preset-modules/blob/6155d0ddd2ba47d1d325659989e80e8a659d0e13/src/plugins/transform-async-arrows-in-class/index.js#L31). Here's the bug [reproduced in the Babel repl](https://babeljs.io/repl#?browsers=edge%3E%3D16%2Csafari%3E%3D10.1&build=&builtIns=false&corejs=3.6&spec=false&loose=true&code_lz=MYGwhgzhAEBiD29oFMAeAXZA7AJjAQmAE7QDeAUNNMPFhOkQK7DrxEAUAlGZVdBIwAOyDpwDcvKpOhZkAd2gAFIvAC2ASwjJ2kAJ5Zg0EgF4AfDz58BwogDoAZoi4TLVdfejsGjZN1Eu-AF9xXkDyQKA&debug=false&forceAllTransforms=false&shippedProposals=false&circleciRepo=&evaluate=true&fileSize=false&timeTravel=false&sourceType=module&lineWrap=true&presets=env&prettier=false&targets=&version=7.14.3&externalPlugins=). I've opened babel/preset-modules#31 to track getting a fix in. In the meantime, the quick...

I think there might be a way to do this by customizing the `public` option to point to `dist`, but I need to give it a try using your example.

Just to clarify: this only happens when running `microbundle --target node`, right? It wasn't included in your examples, but it seems to be the root cause here. We don't use...

@simnalamburt the two changes in #707 should still fix this, including for the browser target. The issue was that we had regenerator manually turned on because it isn't handled by...